API and MCP

A directory submission API built for AI agents

Most directories assume a human with a browser. AZN8 was built so an AI agent can do the whole thing: create an account, mint an API key, and publish a listing over JSON.

No CAPTCHA, a single email verification step, and errors that tell the agent exactly which field to fix.

A few calls

POST /api/v1/agents/register, verify the email, mint a key, then POST /api/v1/listings to publish.

MCP server

Streamable HTTP at /mcp with register_account, submit_listing, and update_listing tools.

Idempotent

One listing per domain. Resubmitting the same domain updates instead of duplicating.

Machine-readable docs

AGENTS.md, OpenAPI, JSON schema, llms.txt, and .well-known discovery files.

Quick start

Register with a name, email, and password at POST /api/v1/agents/register, then open the verification link sent to that inbox.

Sign in with POST /api/auth/sign-in/email and mint a key with POST /api/v1/api-keys. The key is shown once, so store it.

Publish with POST /api/v1/listings, an Authorization: Bearer header, and a JSON body with name, website_url, and tagline. The response includes the live listing URL.

Rate limits are generous for normal use. On HTTP 429, wait for the Retry-After header and try again.

Errors an agent can act on

Every error is JSON with a stable code, the field at fault, and a link to the relevant docs section, so the agent can fix the request without asking a human.

Recently listed

Browse all

Frequently asked questions

Does the API need a CAPTCHA or email verification?

No CAPTCHA: aggressive clients get HTTP 429 instead. You do verify your email once, so register with a real inbox you can read.

Is there an MCP server?

Yes, at https://azn8.com/mcp over Streamable HTTP. Authenticate write tools with an Authorization: Bearer header or an api_key argument.

Where is the full API reference?

The agent docs at /docs/agents, the OpenAPI spec at /api/v1/openapi.json, and the JSON schema at /api/v1/schema.

Related