Developer Quickstart Playbook
Ship your first AGNT integration in under an hour — API auth, MCP server, and A2A end-to-end test.
Why this playbook
AGNT's API has 15 tools, 3 auth flows, and an A2A protocol layer. Jumping straight into the docs works if you already know the data shapes, but most developers waste the first hour figuring out the authentication dance and the venue search response format.
This playbook walks you through three prompts that build on each other: authenticate and make your first API call, scaffold an MCP server that wraps the API, and write end-to-end tests for agent-to-agent communication. Each step produces working code, not pseudocode.
Designed for the developer who wants to ship a working integration in a single sitting, not read docs for a week.
Prerequisites
- AGNT API key — sign up at agntdot.com/developers
- Node.js 20+ or Python 3.11+ installed
- Claude Code, Codex CLI, or any LLM with function calling
- Basic familiarity with REST APIs
Input requirements
| Input | Type | Required | Description |
|---|---|---|---|
| AGNT API key | string (Bearer token) | Yes | Your API key from the AGNT developer dashboard. Free tier supports 1,000 requests/day. |
| Target language | string | No | TypeScript (default) or Python. The prompts adapt their output to your language choice. |
| Use case | string | No | Optional: describe what you're building (e.g., 'Slack bot for venue search') so the prompts tailor their examples. |
Step-by-step workflow
Authenticate and make your first API call
Open promptThis prompt scaffolds authentication, makes a venue search call, and prints the response shape. It teaches you the data model by example, not by making you read a schema doc.
Output: a working script that authenticates, searches for venues in Bali, and pretty-prints the results. You'll reference this response shape in the next two steps.
Scaffold a production MCP server
Open promptTakes the API patterns from step 1 and generates a full MCP server with tool definitions, input validation, and error handling. The server exposes AGNT's API as MCP tools that any Claude Code session can use.
The scaffold includes a test harness — you can verify the server works locally before deploying.
Write A2A end-to-end tests
Open promptThe final step writes integration tests that validate the full agent-to-agent communication loop: your agent sends a booking request, AGNT's agent processes it, and your agent handles the response.
These tests catch the most common integration failures: envelope format mismatches, missing required fields, and timeout handling.
Expected outputs
auth-and-search script
Working script with AGNT API authentication and venue search, demonstrating response shapes.
Produced by step 1MCP server package
Production-ready MCP server wrapping AGNT's API with tool definitions, validation, and local test harness.
Produced by step 2A2A test suite
End-to-end tests for agent-to-agent booking flow with envelope validation and timeout handling.
Produced by step 3Tool requirements
- Claude Code or Codex CLI
- Node.js 20+ or Python 3.11+
- AGNT API key (free tier)
Troubleshooting
API returns 401 Unauthorized
MCP server starts but tools don't appear in Claude Code
A2A tests timeout on booking request
Share as social post
Developer Quickstart Playbook 3 steps, 30-45 minutes. Ship your first AGNT integration in under an hour — API auth, MCP server, and A2A end-to-end test. https://agntdot.com/playbooks/developer-quickstart-playbook
214 / 280 chars