List your service on AgentDNS

Be discoverable to every AI agent using the gateway. No MCP server to build, no plugin to maintain. Implement one JSON endpoint, submit, and you're in.

What's in it for you

✓Your API becomes discoverable inside any agent that uses the AgentDNS gateway — Claude, Cursor, custom frameworks, etc.
✓No MCP server to write or maintain. The gateway translates between your manifest and any agent.
✓Open protocol. No partnership, no exclusive contract — just a public spec and a registry.

How it works for providers

1Implement /.well-known/agent on your service domain. It returns a JSON manifest describing your capabilities. See the spec for the full schema.
2Submit your service at /submit. The registry crawls your manifest and validates it.
3We review and list. Verification typically takes ~48h. You get an email when it's done.

Manifest

A small JSON document describing your API. The gateway uses this to tell agents what your service does and how to call it. Each capability points to a detail_url for a deeper drill-down (method, parameters, examples) — agents only fetch this when needed.

Minimal manifest

{
  "spec_version": "1.0",
  "name": "My API",
  "description": "What my API does in one sentence.",
  "base_url": "https://api.example.com",
  "auth": { "type": "none" },
  "capabilities": [
    {
      "name": "get_data",
      "description": "Fetch data from the API",
      "detail_url": "/api/capabilities/get_data"
    }
  ]
}

We provide SDKs for Express, FastAPI, Next.js, and Spring Boot that generate the endpoints automatically. See the GitHub repo or the full spec.

Pricing & billing

AgentDNS is a single-tenant aggregator: users pay AgentDNS, AgentDNS pays providers. There's no marketplace billing setup for you to go through.

Free services

Nothing special to do. Users authenticate to your service via their own OAuth or your standard auth, through the gateway. We never sit in the billing path.

Paid services (v1)

In v1, AgentDNS itself is your customer. We open an account on your service, hold our own credentials, pay you per our standard billing terms, and re-bill our users on top. From your side it looks like a single high-volume customer — no per-end-user accounts to manage, no Stripe Connect, no marketplace plumbing.

We're working on a partner program for direct billing in a future version. It is not available yet.

No more Stripe Connect

The previous marketplace flow (per-provider Stripe Connect onboarding, per-user subscriptions) was removed. If you were halfway through that setup, you can stop — nothing on your end is required for the v1 billing model.

Spec compliance

The full Agent Discovery Protocol specification: /docs/spec. It covers the manifest format, the auth object, capability detail format, and all required fields.

Trust levels

Each registered service has one of three trust levels. Higher trust means better placement in agent search results and active health monitoring.

VerifiedHighest trust

Your service hosts its own /.well-known/agent. The registry crawls it on a schedule and confirms it's live.

CommunityMaintained by AgentDNS

Manifest hand-written by the AgentDNS team based on your public docs. No infrastructure change on your side. If you want to upgrade to verified, just host the manifest yourself.

UnverifiedNot yet reviewed

Newly submitted, awaiting review. Hidden from search by default.

More detail in /docs/trust-levels.

Get listed

Implement /.well-known/agent, submit your domain, and we'll review within 48h.

Submit your service