Sign in

Documentation

API Documentation

45 REST APIs behind one key and one monthly credit balance; 50 of them have a full reference below. JSON over HTTPS, no SDK required.

Quick start

  1. 1 Get an API key. Sign up free and create a key on the API Keys page — 1,000 credits a month, no card.
  2. 2 Make your first call. Any HTTP client works — pass the key in the X-Api-Key header.
  3. 3 Track your usage. Credits, latency and errors per key on your dashboard's Usage page, once you've signed up.
bash
curl https://api.apicodex.io/countries/v1/all \
  -H "X-Api-Key: $APICODEX_KEY"

Working with an AI agent? Skip the code.

Connect Claude, Cursor or any MCP client to mcp.apicodex.io and ask in plain words: your agent finds the API, reads these docs and makes the calls, on the same credits.

Connect your agent

Authentication

Every request carries your key in the X-Api-Key header. Keys start with acx_live_ and belong to your team — every key shares the team's plan and credit balance.

Keep keys server-side. A compromised key can be revoked instantly; revocation takes effect within minutes.

Credits & rate limits

Each call spends credits from one monthly balance: cheap lookups cost 1, heavyweight scrapes cost more. The exact cost of every endpoint is on the pricing page and in each API's reference below, and every response says what it cost in its X-Credits-Charged header.

Requests per second is capped per plan. Over quota or over the rate limit, the gateway answers 429 until the billing period rolls over or you back off.

Errors

Failures are JSON with an error message and a conventional status code:

400Bad request — a required parameter is missing or malformed.
401Missing, invalid or revoked API key.
403Key suspended — contact support.
404Unknown endpoint — check the path against the reference below.
429Over the plan's credit quota for this period, or over the per-second rate limit.
5xxUpstream failure — safe to retry with backoff; failed calls still show on your Usage page.

Reference

Every API, straight from the spec

Each reference is rendered from its OpenAPI spec (/openapi/{api}.yaml): parameters, responses and examples. The specs are maintained by hand and ship with each release of this site.

Email

Document Parsers

Text Intelligence

Web Intelligence

Infrastructure

Data & Reference

Developer Tools

Web Scraping

Social Media