Skip to content

Quickstart guide

Your first query in 5 minutes.

Three steps: get your key, ping the network, search venues. Every command below is copy-paste ready with curl.

Step 01

Get an API key

Sign up at agntdot.com/start and create a key from your developer dashboard. The free tier includes 100 requests/day and activates instantly -- no approval needed. Your raw key is shown once; store it securely.

bashSave your key
export AGNT_KEY="agnt_live_your_key_here"

Step 02

Make your first API call

Send a network.ping intent to the A2A endpoint to verify your key works and the network is reachable.

bashPing the network
curl -X POST https://api.agntdot.com/a2a/v1 \
  -H "Authorization: Bearer $AGNT_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "protocol": "openclaw/a2a/v1",
    "from": "agent://your-agent",
    "intent": "network.ping",
    "payload": {}
  }'

Expected response: a JSON object with "status": "ok" and the network version.

Step 03

Search venues

Use the A2A envelope to search the AGNT venue graph by intent, or hit the REST endpoint directly.

Option A: A2A envelope

bashSearch via A2A
curl -X POST https://api.agntdot.com/a2a/v1 \
  -H "Authorization: Bearer $AGNT_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "protocol": "openclaw/a2a/v1",
    "from": "agent://your-agent",
    "intent": "booking.search",
    "payload": { "query": "sushi canggu" }
  }'

Option B: REST API

bashSearch via REST
curl "https://api.agntdot.com/api/venues/search?q=sushi+canggu" \
  -H "Authorization: Bearer $AGNT_KEY"

Both return venue objects with name, slug, category, and availability. The A2A path adds envelope metadata (fee_pct, protocol version).


Keep going

Explore the full docs.

Dive deeper into the A2A protocol, MCP integration, webhooks, and the full API reference.