For API vendors

List your API on Connect.

Connect gives agents one key for 59 providers and 318 operations. Your agent reads our guide, writes the listing and opens the PR.

Why list

Be one of the providers Connect routes to.

Reach agents where they already call

Agents and backends use Connect through one key. Your operation shows up in the same catalog as the rest, with no integration for each buyer to build.

A typed, priced operation

Your endpoint becomes an operation with a JSON Schema and a fixed price per call. Buyers see the cost before they run it.

Routed traffic, not a link

Connect ranks providers per operation and sends calls to the first one that answers. Being listed puts you in that ranking.

No sign-up flow to run

Buyers hold one Connect key and one balance. You do not need to onboard, bill or support each of them separately.

Reviewable in the open

The listing is a pull request against an open source repo. You can see exactly how your API is called and what is logged.

Limits you set

You tell us your concurrency and per-minute limits. Connect enforces them in front of your API, across every worker.

How

Four steps, one of them is a paste.

  1. 01

    Create an account

    Sign up on Konnect. The account is how we know who the vendor is and where to send questions about your listing.

    Create an account
  2. 02

    Open your coding agent

    Claude Code, Cursor, Codex or any agent that can run commands. Before you start, sign in to the GitHub CLI (gh auth login) and set up commit signing. The agent forks the repo for you.

  3. 03

    Paste one line

    Add your docs URL. The agent reads your docs and pricing, shows you one table to confirm, writes the operation and adapter, runs the tests and opens the PR.

  4. 04

    We review

    We check schema, limits and failure handling. Once it passes, your operation joins the catalog.

paste into your coding agent
Read https://dashapi.ai/connect/vendor-listing.md and list our API on DashAPI Connect.
Our docs are at <YOUR API DOCS URL>. Fork the repo, build the listing and open the PR.

Replace the docs placeholder, then run it in any empty folder. The agent forks dashapi-connect for you.

Safe by default

Your agent works on its own branch, and signs every commit.

A dedicated branch

The agent creates a branch named add-your-vendor-provider in your fork and works only there. It never commits or pushes to main, and it checks the branch name before it commits and again before it pushes. Nothing reaches us except a pull request.

Signed commits

Every commit is signed, so we can see it came from you. The agent commits with git commit -S, then checks the signature before it pushes. GPG and SSH signing both work.

Set up signing before you start

If signing is not configured, the agent stops and points you to GitHub's setup guide. It will not turn signing off to get past the check. For GitHub to show a commit as Verified, add your signing key to your GitHub account. GitHub's signing guide

What your agent will ask

Have these ready.

  • Which endpoints become operations (the agent proposes them from your docs)
  • Price per call, in USD, and whether bulk or batch requests cost less
  • Your rate and concurrency limits
  • A sandbox key for tests (never committed)
  • Whether data is public or tied to the buyer's own account
  • For personal data: where it comes from, your lawful basis, your DPA and sub-processor list, where it is stored, and how people opt out or delete

The agent writes the answers into the pull request, so we can read your reasoning, not just your code.

What we review

Schema
Inputs and outputs are bounded JSON Schema. Output has the same shape whichever provider answers.
Limits
Concurrency and per-minute limits match what your plan allows.
Failure handling
No match, rate limit, timeout and bad input each return the right outcome, so routing and billing behave.
Secrets
Keys come from configuration. Nothing sensitive is logged.
Personal data
Operations that return personal data declare the categories and the privacy details above. We record what you state and link your documents. We do not certify compliance for you.
Effect
Reads go through the standard path. Writes and spend actions need human approval and are reviewed separately.

Where this stands

Vendor listing is in beta and every listing is reviewed by hand. Commercial terms, such as how listed vendors are paid, are agreed per listing and are not published yet. Ask when you open the pull request, or write to us first.

Ready to list?

Create an account, then hand the guide to your coding agent.