We launched Wayforth as "the search engine and payment rail for AI agents."
That description was accurate. It just wasn't the
whole picture — and in some ways it was pointing at
the wrong thing.
Since then we've shipped 10 production releases,
removed a token we were planning to launch, rebuilt
the ranking algorithm, added two payment rails,
launched a provider intelligence dashboard, and
listed on x402scan and Agentic.Market.
Here's the honest version of what happened.
What Wayforth actually is
Wayforth is an API runtime for autonomous AI agents.
One MCP install. 3,000+ services. Three payment
rails. Discovery, payment, and execution in a
single tool call.
uvx wayforth-mcp
Your agent can now do this:
# Search by intent — plain English
wayforth_search("translate to Spanish")
# → DeepL WRI:82 · $0.00003/call · card | usdc | x402
# Execute — no API key needed
wayforth_execute(slug="deepl", text="Hello")
# → "Hola" · 312ms · 1 credit
No API key for DeepL. No DeepL account. No
integration code. Wayforth holds the key,
your agent gets the result.
That works for 15 managed services today. For
the other 3,000+ in the catalog, you bring your
own key and Wayforth handles the proxy,
monitoring, and payment.
The thing we got wrong
When we launched, we were planning a $WAYF token.
Staking pools. Verifier networks. Token-gated
rankings. The whole thing.
We cut all of it.
The token complicated the story, added regulatory
risk, and — most importantly — wasn't necessary.
WayforthRank doesn't need a token to be
defensible. It needs payment signal. And payment
signal comes from real agents paying real money,
which we can track without a blockchain token.
Wayforth is a centralized infrastructure company.
We own the ranking algorithm. We hold the managed
keys. We process the routing fees. That clarity
is the product.
What WayforthRank actually does
This is the part worth understanding.
Every service in the Wayforth catalog has a WRI
score from 0–100. The score is computed from:
- Verified payment signal (real agents paying)
- Uptime over the last 7 days
- Average response latency
- Tier verification status
- x402 support
The payment signal is what makes it defensible.
A service can't buy a higher ranking — it can
only earn one. And the signal only accumulates
through Wayforth, which means it can't be
replicated by a directory or a payment processor
working separately.
We formalized this as the WayforthRank
Integrity Policy — permanently legally
enforceable, built into our Terms of Service:
No service can pay to rank higher.
Zero sponsored placements.
No advertising model. Ever.
Three payment rails
One of the biggest changes since launch: we
moved from crypto-only to three parallel rails.
Track A — Card (Stripe Treasury)
No crypto required. Developer tops up with a
credit card, calls execute, Wayforth routes
the credit. Mainstream developer, no wallet needed.
Track B — USDC on Base
Non-custodial. Agent holds its own wallet,
signs a transaction, WayforthEscrow routes
the payment on-chain.
Track C — x402
HTTP 402 native. Agent pays and retries in
one round-trip via Coinbase CDP.
Same 1.5% routing fee on all three. Same
WayforthRank signal from all three.
Self-healing payments
Shipped in v0.6.10 this week.
If an API call fails — 5xx, timeout, unreachable
— credits restore automatically. No dispute
process. No support ticket. No human in the loop.
{
"error": "Service unavailable",
"refunded": true,
"credits_restored": 1,
"calls_remaining": 3498
}
The WRI penalty still applies — a failed call
counts against the service's rank. But the
developer doesn't pay for it.
The numbers
- 3,271 services across 19 categories
- 809 Tier 2 verified (probed every 6h, auto-demoted on 3 consecutive failures)
- 277 x402-native services
- 15 managed services (zero API key needed)
- 298+ production API routes
- 133/133 end-to-end tests passing
What we built for providers
The Provider Dashboard launched as a separate
B2B product in v0.6.8.
Providers see:
- Every search query that surfaced their service
- WRI score breakdown and history
- Anonymized competitor comparison
- Masked agent IDs and call patterns
- Estimated earnings at 98.5% of every payment
This was a deliberate choice: providers should
have enough intelligence to improve their service
and earn better rankings — but not enough to
game the system.
The x402 ecosystem
We're now listed on x402scan as a native seller:
GET https://gateway.wayforth.io/x402/search
→ HTTP 402
{
"x402Version": 2,
"accepts": [{
"scheme": "exact",
"network": "eip155:8453",
"amount": "2000",
"asset": "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913",
"payTo": "0xb59f678a1bd568b3599756947ad965760038cf40",
"maxTimeoutSeconds": 300
}]
}
$0.002 USDC per search query. An agent can
discover and pay for Wayforth without any
prior relationship or API key.
We're also x402 v2 compliant with Bazaar
discovery extension — Agentic.Market indexes
us automatically when the first real payment
goes through.
What's next
v0.7.0 — Gravity.
First real revenue. Stripe subscriptions live.
Provider payouts. Base mainnet deployment
(post-audit). The flywheel starts.
If you're building AI agents and need external
APIs, try it:
uvx wayforth-mcp
100 free calls. No card. No setup.
GitHub: github.com/WayforthOfficial/wayforth
Docs: wayforth.io
Top comments (0)