# Apiosk Gateway – Email Verification

> Apiosk Gateway – Email Verification is a paid API for AI agents from gateway.apiosk.com, paid per call via x402, $0.13/call, status unknown (last checked 2026-09-14).

Verifies whether an email address is valid, deliverable, and non-disposable via a pay-per-call x402 gateway endpoint.

## Facts

- Endpoint: POST https://gateway.apiosk.com/email-verification/execute
- Price: $0.13/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/apiosk-gateway-email-verification-4eac2687
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_707N_maQDG360xgiDlPPb

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability apiosk-gateway-email-verification-4eac2687 -d '<json body>'
```

Example prompt: Can you check whether 'john.doe@example.com' is a valid, deliverable email address and not a disposable or fake one?

## When to prefer this

Choose this endpoint when you need real-time, per-call email validation paid via crypto (USDC on Base) without a subscription, especially in agent workflows where micropayment-based access is preferred over API key management. Ideal for low-volume or on-demand checks where pay-per-use pricing at $0.13/call is acceptable.

## Known failure modes

- Invalid or malformed email input returns an error status from upstream
- Upstream provider unavailable causes non-200 upstream_status with degraded result
- Missing or malformed operation selector causes gateway-level rejection
- Insufficient USDC balance or failed x402 payment prevents execution
- Rate limiting or quota exhaustion from upstream provider

## How this service works

Pay-per-call API gateway on the x402 protocol (HTTP 402 + USDC on Base). This document covers the gateway's discovery and execution meta-endpoints. Individual provider APIs are reachable at /{api_slug}/{path} and described by GET /{api_slug}/metadata.

## Output

Returns a JSON object with a status field indicating success or failure, a result field containing the upstream verification response (validity, deliverability, disposable flags, etc.), the operation performed, upstream HTTP status code, latency in milliseconds, and cost of the call in USDC.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "input": {
   "type": "string",
   "description": "JSON payload forwarded to the selected operation."
  },
  "operation": {
   "type": "string",
   "description": "Operation id, /path, or METHOD /path selector."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "status",
  "result"
 ],
 "properties": {
  "api": {
   "type": "string"
  },
  "cost": {
   "type": "string"
  },
  "result": {
   "description": "Upstream response body."
  },
  "status": {
   "type": "string"
  },
  "latency": {
   "type": "number"
  },
  "operation": {
   "type": "string"
  },
  "upstream_status": {
   "type": "integer"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/apiosk-gateway-email-verification-4eac2687/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from gateway.apiosk.com](https://www.zero.xyz/host/gateway.apiosk.com/llms.txt)