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.
For API vendors
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
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.
Your endpoint becomes an operation with a JSON Schema and a fixed price per call. Buyers see the cost before they run it.
Connect ranks providers per operation and sends calls to the first one that answers. Being listed puts you in that ranking.
Buyers hold one Connect key and one balance. You do not need to onboard, bill or support each of them separately.
The listing is a pull request against an open source repo. You can see exactly how your API is called and what is logged.
You tell us your concurrency and per-minute limits. Connect enforces them in front of your API, across every worker.
How
Sign up on Konnect. The account is how we know who the vendor is and where to send questions about your listing.
Create an accountClaude 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.
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.
We check schema, limits and failure handling. Once it passes, your operation joins the catalog.
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
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.
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.
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
The agent writes the answers into the pull request, so we can read your reasoning, not just your code.
What we review
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.
Create an account, then hand the guide to your coding agent.