// routing + settlement layer for AI agents
The execution fabric for AI agents.
One connection. Every capability.
TESSL lets agents call capabilities instead of vendors. Requests are routed in real time by price, latency, reliability, and reputation, then settled through one payment layer.
// how it works
One call. Best route.
Call
Your agent calls a capability, not a vendor.
Route
TESSL compares providers by price, latency, reliability, and recent performance.
Settle
The winning service executes the request, payment clears, and the result returns through one response.
// why tessl
Agents should not manage vendor chaos.
Autonomous workflows are forced to juggle API keys, pricing models, rate limits, uptime gaps, and payment flows. TESSL turns that mess into one routing layer.
// integration
Three lines. Every microservice.
{
"mcpServers": {
"tessl": {
"url": "https://mcp.tessl.xyz",
"headers": {
"Authorization": "Bearer sk-tessl-..."
}
}
}
}// wallet
One wallet. Every protocol.
Fund once. Reach every microservice. You set the limits.
Top up your TESSL wallet with USDC, set spend boundaries, and let agents pay per request without managing vendors directly.
Daily spend limit
250 USDC
Approval threshold
5 USDC
Low balance alert
20 USDC
Per-call cap
0.50 USDC
Allowed categories
// directory
Capability directory, not an API graveyard.
Image generation
// generate_image
Search
// search_web
Voice
// text_to_speech
Video
// generate_video
Translation
// translate_text
Code execution
// run_code
Data extraction
// extract_data
Web browsing
// browse_url
Research
// deep_research
Memory
// store_memory
Automation
// run_workflow
Robotics tools
// actuate_device
// live routing
Routing changes with the market.
A live view of how capabilities map to providers as conditions shift.
| Capability | Provider | Price | Latency | Reputation | Route state |
|---|---|---|---|---|---|
| generate_image | flux | 0.012 | 420ms | high | selected |
| search_web | tavily | 0.004 | 280ms | high | selected |
| text_to_speech | cartesia | 0.007 | 610ms | medium | fallback |
| run_code | e2b | 0.010 | 1.2s | medium | degraded |
| deep_research | exa | 0.018 | 900ms | high | bidding |
| translate_text | deepl | 0.003 | 210ms | high | paused |
// reputation
Every response teaches the router.
TESSL does not route from a static list. It learns from response time, failed calls, price consistency, fulfillment quality, and settlement history.
// $TSSL utility
$TSSL coordinates access to the routing layer.
TESSL is the product. $TSSL unlocks deeper routing, expanded directory access, higher request throughput, advanced spend controls, provider reputation data, and future network modules.
Basic
- limited routing
- standard directory
- simple wallet controls
Operator
- higher request throughput
- saved routing preferences
- provider reputation view
Builder
- API access
- advanced budget rules
- webhook events
- private service lists
Network
- provider tools
- routing data access
- future module activation
// network modules
// docs
Built like infrastructure. Read like a router manual.
Quickstart
Connect an agent in three lines.
read →MCP Integration
Wire the MCP server into any client.
read →Wallet Funding
Top up USDC and set spend limits.
read →Routing Logic
How providers are ranked and selected.
read →Settlement Model
Per-request payment and clearing.
read →Provider Directory
Browse available capabilities.
read →Reputation Spec
Signals that shape the router.
read →x402 Client
Pay-per-request over HTTP 402.
read →Provider Onboarding
SOONJoin the provider mesh.
Self-hosted Router
SOONRun the router on your own infra.
Dispute Layer
SOONResolution for failed settlements.
The routing layer for AI agents.
One MCP connection. Thousands of services. Pay per request in USDC.