DashAPI Connect · Open source

One key to every tool your agent needs.

Skip the signups, keys and invoices. 318 operations across 59 providers behind one key.

Live routing, simulated
POST /v1/operations/person.profile.find
{ "name": "Ada Okafor", "company": "northwind.io" }
  1. apolloNo match · 410 ms
  2. lushaMatch, 3 fields · 780 ms
Profile resolved via lusha$0.0250
318
operations

Typed, validated, versioned

59
providers

Behind one key

7
categories

Enrichment to market data

99.95%
routed success

After fallback, trailing 30 days

ExaFirecrawlSemrushDataforseoApolloHunterSerperTavilyCrunchbasePerplexityLinkedinSlackOpenrouterReplicateScrapecreatorsZerobounceLushaLeadmagicMozMajesticPolygonFinnhubBrightdataApifyExaFirecrawlSemrushDataforseoApolloHunterSerperTavilyCrunchbasePerplexityLinkedinSlackOpenrouterReplicateScrapecreatorsZerobounceLushaLeadmagicMozMajesticPolygonFinnhubBrightdataApify

Built for customer-facing teams working in

HubSpotSalesforcePipedriveZendeskIntercomSlackLinkedInMailchimpNotionGmailZoom

Sales · Marketing · Customer success · Support

Names and logos belong to their owners and appear only to describe the tools these teams use. No affiliation or endorsement is implied.

Why Connect

Your agent should spend its time on the task, not on accounts.

One key, 59 providers

Skip the signups, the invoices and the key files scattered across repos. Connect holds the provider accounts. You hold one revocable key.

Routing that checks the evidence

Each operation has a ranked list of providers. When one has no answer or is down, the next one takes the call and your agent still gets a result.

Pay for what comes back

Prices are fractions of a cent per call and visible before you make it. Already have a Semrush plan? Bring the key and keep it.

Smart routing

When one provider stumbles, the call keeps going.

Ordered by evidence
Each operation has a ranked list of providers. Rank comes from measured success, speed and price on that operation, not on the provider as a whole.
Only the right failures fall back
No match, rate limit and provider outage move on to the next provider. A bad credential or a refused request stops, so we never hide a real error.
Writes are never replayed blindly
If a timeout might have happened after a provider acted, Connect records an uncertain outcome and reconciles it instead of sending the write again.
How routing works
connect.sh
# one key, any operation$ curl https://api.dashapi.ai/v1/operations/person.profile.find \    -H "Authorization: Bearer $CONNECT_KEY" \    -d '{"name":"Ada Okafor","company":"northwind.io"}' {  "status": "succeeded",  "data": { "profile_url": "linkedin.com/in/ada-okafor", "title": "VP Sales" },  "route": [    { "provider": "apollo", "outcome": "no_match" },    { "provider": "lusha",  "outcome": "match" }  ],  "cost_usd": "0.0250"}

Routing profiles · Coming next

Optimized routing for

Try the provider with the best measured success rate for this operation first. Falls back in order of success, so the call lands as often as it can.

Request

web.contents.get

Connect

Reliability first

firecrawl99.4%
exa98.1%
tavily96.7%

Success rate

Calls routed 0Fallbacks 0Highest first. Next provider takes over on a failure.

How it works

From signup to first result in four steps.

  1. Get a key

    Sign up on Konnect, fund your balance and create an API key. Revoke it any time.

  2. Call an operation

    One endpoint, one schema per operation. Connect picks the provider.

  3. Connect falls back

    If a provider has no match or goes down, the next one answers. You get one result.

  4. Pay for what came back

    Prices show before each call. A balance, not seats. Cache hits are billed at the same price.

Connect

The engine. Open source.

Routing, caching, credentials, accounting and audit. One container, one PostgreSQL database. Read every line, change what you need, run it where your data lives.

Run Connect yourself

Konnect

The hosted version.

We run Connect for you and add a portal: sign in, fund your balance, create keys, set spending limits and watch usage by key.

Try it on Konnect

Trust

Your data passes through.
Your keys never do.

Keys stay server-side

Provider credentials are injected on our side. Your agent never sees one, and logs never contain one.

Your answers stay yours

Answers obtained with your own provider keys never enter the shared cache. They are cached for your organization only.

Open to audit

Every call lands in an append-only audit trail, and the engine is open source. Read how it works instead of taking our word.

Built for teams. Fine for one.

Scoped keys, spending limits and an audit trail for a security review. The same API and the same price list for a founder with a single key.

Never trained on

Connect is not a model and does not train on what you send. Each provider sets its own terms, and the catalog shows who answers each operation.

SOC 2 Type II: not yet

There is no SOC 2 report today and we will not imply one. The controls are built to be audited: append-only logs, scoped access and open code.

All security controls

FAQ

Straight answers.

What is the difference between Connect and Konnect?

Connect is the open-source service that does the work: routing, caching, credentials and accounting. Konnect is the hosted portal we run on top of it, where you sign in, add credit, create keys and watch usage. You can use Connect without Konnect.

Do I need to open an account with each provider?

No. Managed operations run on DashAPI provider accounts and you pay per call. If you already pay for Semrush or another supported tool, bring your own key and keep your contract.

What happens when a provider is down?

Connect tries the next provider for that operation, within limits on time and spend. The response lists every attempt, so you can see what happened and what it cost.

Is there a markup on provider rates?

Prices are set per operation and shown before the call. Bring-your-own-key calls are covered by your plan.

Can I run it myself?

Yes. Connect ships as one container image with a PostgreSQL database. The repository has the API contract, migrations and deployment notes.

How does it work with agents?

Connect is a plain HTTP API today. A public MCP adapter is built but not switched on yet, because we want the authorization model right first.

Where does my data go?

Public-data answers can be served from a shared cache. Answers from your own keys never enter it. Konnect runs on AWS, with regions across North America, Europe, Asia and Latin America being rolled out. Choosing a region for your data is not available yet.

Give your agents one key.

Start on Konnect in a few minutes, or clone the repo and run Connect yourself.