For agent builders
Ask Odeals before your agent says a task is doable.
An AI agent can ask Odeals whether networkers list Services for a task, in its domain and country, without an account. It pays a fraction of a cent per question from prepaid credit. The answer reports what members have listed. It never promises an outcome.
Pricing
| Query | Price | What it returns |
|---|---|---|
| Feasibility check | $0.009 | Is this task something networkers on Odeals list services for, in this domain and country? A verdict, match counts and the rules that apply. |
| Match report | $0.09 | The feasibility check plus fee ranges, network depth, terms and up to five public teasers. |
- Members get their own key on the Account page, with queries included every month: $5 on Member, $25 on Principal, $150 on Institution. The allowance is spent first and resets on the 1st.
- Credit is prepaid from $5 and stays valid for 12 months.
- You are not charged for tasks we cannot map to a domain, prohibited tasks, refused requests, or retries with the same Idempotency-Key within 24 hours.
- The agent API is for agents without an account. A Member seat ($199 a month) includes unlimited market searches on Odeals, plus bidding, NDA rooms and introductions. Above 2,211 match reports a month, a Member seat costs less. See membership
What an agent sees
What an agent gets
- A verdict on whether networkers list Services for the task, with counts by country and region
- The exchange rules that apply, including which fee models a networker may earn
- In a match report: fee ranges posted by members, terms, network depth and up to five public teasers
What an agent never gets
- NDA-gated details, confidential parties or hidden figures
- Any way to contact a networker: a person needs an Odeals account for that
- A promise of funding, an approval, a licence or a closed deal
Quick start
1. Create a free key. It is shown once; Odeals keeps only a hash.
curl -X POST https://odeals.app/api/agent/v1/keys \
-H "content-type: application/json" -d '{"label": "my-agent"}'2. Top up credit. Checkout returns a URL for a person to pay by card.
curl -X POST https://odeals.app/api/agent/v1/topups \
-H "authorization: Bearer $ODEALS_API_KEY" -H "content-type: application/json" \
-d '{"amount_usd": 5, "method": "checkout"}'3. Ask. Send an Idempotency-Key so a retry is never charged twice.
curl -X POST https://odeals.app/api/agent/v1/feasibility \
-H "authorization: Bearer $ODEALS_API_KEY" -H "content-type: application/json" \
-H "idempotency-key: 4f1c-task-001" \
-d '{"task": "Get approval to run an insurance pre-licensing school in New York State"}'Free endpoints: GET /api/agent/v1/pricing, GET /api/agent/v1/domains and GET /api/agent/v1/balance.
How an agent pays
- Card, through Stripe Checkout. A person tops up the key once from a browser.
- Stripe Shared Payment Token. An agent platform grants a scoped token and the agent sends it with
"method": "spt". No card details reach Odeals. - HTTP 402 challenge. A request with no credit gets
402 Payment Requiredwith a Machine Payments Protocol challenge inWWW-Authenticate: Payment, so an agent that speaks the protocol can pay a top-up and retry. - Stablecoin sessions. True per-query payments over the Machine Payments Protocol are planned. They are not live yet.
Every paid answer carries a Payment-Receipt header and a billing block with the cost and the balance left.
MCP server
The MCP endpoint is https://odeals.app/api/mcp (Streamable HTTP, JSON responses). Its tools: odeals_check_feasibility, odeals_match_report, odeals_list_domains and odeals_pricing_and_balance. Paid tools draw on the same credit.
For a client that launches a local command, use the stdio bridge in the app repository:
{
"mcpServers": {
"odeals": {
"command": "node",
"args": ["<path to app>/scripts/odeals-mcp-stdio.mjs"],
"env": { "ODEALS_URL": "https://odeals.app", "ODEALS_API_KEY": "odk_test_..." }
}
}
}