> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Use Meer API in Deepline

> Connect your own Meer API key. Includes SDK V2 and CLI requests, input constraints, response fields, and Deepline credit cost.

[Human guide: work with your agent →](https://deepline.com/docs/human/providers/meerapi/guide.md)
Inspect one Meer API action before starting provider-backed work. Your first result is a verified input and output contract.

## Provider-specific requirements

* Meer checks a phone number against its country's national do-not-call register. It answers `do_not_call` true or false. It does NOT report whether a number is valid, its line type, or its carrier. Do not use it as a phone validity or line-type validator. Use a phone validator for that.
* Good fit as a compliance gate after phone discovery and validation: drop or flag numbers with `do_not_call: true` before dialing or texting.
* Send E.164 with the national leading zero dropped (UK 01000822380 is +441000822380). Deepline rejects numbers that are not E.164 (leading `+`, digits only) before calling Meer, because Meer charges for numbers its register marks invalid. Unsupported countries return a 422 listing supported countries.
* Requires your own Meer API key. Deepline does not bill for Meer. Meer charges credits to your account and the cost varies by country. The response does not include the credit cost. See your Meer dashboard.
* Webhook mode (`webhook_url`) and the reseller `X-Forwarded-Host` header are not exposed. Calls are synchronous.
* `meerapi_get_usage_stats` reads your request counts (total, monthly, by country) and is free. Billing-period credit usage is not exposed.

## Find an applicable action

Confirm your effective workspace, then search the live catalog:

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline auth status --json
deepline search "Meer API" --type tools --json
```

Search returns candidates. Check the returned provider and operation rather than selecting a similar title automatically.

## Inspect the selected contract

Replace `<returned-tool-id>` with the identifier returned by discovery:

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline describe <returned-tool-id> --json
```

These commands do not execute the selected provider action. Read its required inputs, supported access mode, pricing unit, outputs, and limits.

A connection does not establish that every action supports BYOK. Follow the provider-specific requirements above and the live action contract.

## Prepare one reviewed input

Use one authorized record that matches the inspected schema. Preserve its source identity and define the result you will accept.

Open the action reference for its payload and response shape. Provider-backed execution can incur usage or external effects.

For reusable logic, follow [Write Plays](https://deepline.com/docs/sdk-v2/plays.md). For direct-call recovery, use [Tool execution recovery](https://deepline.com/docs/sdk-v2/tool-execution-recovery.md).

> [!TIP]
>
> Continue only when the workspace, provider, required fields, acceptance rule, and applicable price are understood. Keep unavailable access separate from no-result evidence.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.