Smart routing

Providers fail. Your agent should not notice.

Connect ranks providers per operation and falls back when one has no answer. Every attempt is in the response, with its cost.

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

Four rules decide every call.

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.

Bounded, every time

Fallback depth, total time and spend are capped per request. You see every attempt in the response, with what each one cost.

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.

What each outcome does.

OutcomeConnect doesWhy
No matchTry next providerThe provider answered and found nothing.
Rate limitedTry next providerAdmission limits keep us under each supplier quota.
Provider outageTry next providerWithin the time and spend caps for the request.
Uncertain completionReconcile, do not retryProtects writes from being sent twice.
Authorization failureStop and reportA real error is never hidden behind a fallback.

You see the whole route.

The response lists each provider tried, what happened and what it cost. No guessing why a call took 3 seconds.

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"}

See it on your own calls.

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