Submit an API

cn2.ai ships with 160+ built-in providers, but anyone can submit a new API. Submissions go through admin review before appearing in the explorer and becoming available for key listings.

What you need

To submit a provider, you'll fill out a form in the seller dashboard with the following information:

  • Basic info — provider name, slug (used as the subdomain), category, HTTPS base URL, docs URL, brand color
  • Authentication — how the API authenticates requests (bearer token, API key header, basic auth, or query parameter), including the header name and prefix
  • Routes — at least one endpoint with HTTP method, path prefix, description, and optional per-route price
  • Liveness check — a low-cost endpoint cn2.ai can call to verify keys are valid (method, path, expected status code, optional request body for POST endpoints)

Slug requirements

  • 3–30 characters, lowercase letters, numbers, and hyphens only
  • Must start and end with a letter or number
  • Must be unique — not already used by a built-in or community provider
  • The slug becomes the subdomain: your-slug.cn2.ai

Approval process

  1. You submit the provider spec from your dashboard
  2. The submission appears as pending in your submissions list
  3. An admin reviews the spec — they may approve, reject, or request revisions with notes
  4. If revisions are requested, you'll see the admin's feedback and can update your submission
  5. Once approved, the provider appears in the explorer with a "community" badge
  6. Sellers (including you) can now list keys against the approved provider

After approval

Once approved, the provider works exactly like built-in providers:

  • Accessible at slug.cn2.ai
  • Supports MPP and x402 payments
  • Keys are encrypted with AES-256-GCM and decrypted only at request time
  • Automatic liveness checks, priority scoring, and rate limiting
  • Region-aware routing (EU, US, APAC, global)
  • Dashboard analytics powered by Tinybird

Tips for a smooth approval

  • Use the API's official base URL (HTTPS required)
  • Choose a liveness endpoint that's free or very cheap to call (e.g. a models list or health check)
  • Include accurate route definitions — these determine per-route pricing
  • Link to the API's official documentation
  • Pick a brand color that matches the provider's identity