Getting Started
Verify our claims
Marketing pages make claims. This page pairs each one with a command you can run right now against the live API. No account is needed for most of them.
“130+ models behind one API, with public per-model pricing”
The catalog endpoint is public. No API key. Every row carries its own pricing.
curl -s https://api.apexapi.dev/v1/models | jq '.data | length'curl -s https://api.apexapi.dev/v1/models | jq '.data[0] | {id, pricing}'“Drop-in OpenAI compatible”
The chat endpoint accepts the OpenAI Chat Completions request shape and returns the OpenAI response shape. This one needs an ak- key (create one on the keys page, or without a human, see the last claim).
curl https://api.apexapi.dev/v1/chat/completions \
-H "Authorization: Bearer ak-your-api-key" \
-H "Content-Type: application/json" \
-d '{
"model": "openai/gpt-5.5",
"messages": [{"role": "user", "content": "Say OK"}]
}'Or point any OpenAI SDK at base_url=https://api.apexapi.dev/v1. No other code changes.
“The whole platform is machine-readable”
Everything an agent needs to integrate exists as a plain fetchable file: an index, a full OpenAPI 3.1 spec, and an A2A Agent Card at the standard well-known path.
curl -s https://apexapi.dev/llms.txt | head
curl -s https://apexapi.dev/openapi.json | jq '.info'
curl -s https://apexapi.dev/.well-known/agent-card.json | jq '{name, skills: [.skills[].id]}'“Web context: you pay when the fetch is dispatched, not only on success”
POST /v1/scrape bills at whichever rail actually ran ($0.002 standard, $0.008 stealth), including a dispatched failure: a blocked page, an unreachable target, or a page with no extractable content. Only a request rejected before dispatch, an invalid or disallowed URL, is free. Every response, success or billed failure, reports what it cost.
curl -si https://api.apexapi.dev/v1/scrape \
-H "Authorization: Bearer ak-your-api-key" \
-H "Content-Type: application/json" \
-d '{"url": "https://example.com", "format": "markdown"}' \
| grep -iE "x-apexapi-cost|x-apexapi-credits-remaining"To check the free case, submit a private or invalid URL instead: it is rejected with a 400 before any fetch runs, and the X-ApexApi-Credits-Remaining header on your next request is unchanged. A blocked or timed-out page, by contrast, still reports a cost, since the fetch was dispatched. Details: /docs/scrape.
“An agent can onboard with no human in the loop”
The full recipe is a plain markdown file, and registration is one unauthenticated POST that returns a working API key immediately.
curl -s https://apexapi.dev/auth.md | head -30curl -s -X POST https://api.apexapi.dev/agent/register \
-H "Content-Type: application/json" \
-d '{"type": "anonymous"}'The response includes an ak- key, a claim token, and a fund URL anyone can pay by card or USDC on Base. Unfunded, unclaimed accounts are deleted after ~30 days; funded accounts never expire.
Found a claim that does not hold?
Tell us and we will fix the claim or the product: support@apexapi.dev.