# Apiosk Gateway – Frankfurter Execute

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

Executes a Frankfurter currency exchange rate API operation via the Apiosk pay-per-call gateway using the x402 protocol (HTTP 402 + USDC on Base).

## Facts

- Endpoint: POST https://gateway.apiosk.com/frankfurter/execute
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/apiosk-gateway-frankfurter-execute-47815ea9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_DM_xVrPY7QLZzot0mfAxh

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-frankfurter-execute-47815ea9 -d '<json body>'
```

Example prompt: Can you get me the current exchange rate from EUR to USD using Frankfurter — call the latest rates endpoint with EUR as the base currency?

## When to prefer this

Choose this endpoint when you need programmatic, pay-per-call access to Frankfurter exchange rate data (ECB-sourced) without managing API keys, subscriptions, or billing accounts — ideal for agents that need currency conversion or historical FX rates on demand and can pay micro-amounts in USDC via the x402 protocol on Base.

## Known failure modes

- Invalid operation selector — returns error status if the operation ID or path does not match a valid Frankfurter endpoint
- Malformed JSON payload — upstream rejects the request if input JSON is invalid
- Unsupported currency code — Frankfurter returns 404 or error if currency symbol is not in its dataset
- Payment failure — x402 payment not confirmed, gateway rejects the call before forwarding
- Date out of range — Frankfurter only has ECB data from 1999-01-04; earlier dates return an error
- Network/upstream timeout — latency field may be high and result may be null

## 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 containing: status (success/error), the upstream Frankfurter API response body (e.g. exchange rates, time series, or currency list), the operation invoked, latency in milliseconds, HTTP status from the upstream Frankfurter service, and the 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-frankfurter-execute-47815ea9/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)