# KlearFlow Relay

KlearFlow Relay is a machine-paid x402 service for revenue intelligence, revenue recovery, and paid service routing.

Base URL: https://klearflow.vercel.app
MCP: https://klearflow.vercel.app/mcp
x402 manifest: https://klearflow.vercel.app/.well-known/x402
OpenAPI: https://klearflow.vercel.app/openapi.json
Pricing: https://klearflow.vercel.app/api/pricing
Proof: https://klearflow.vercel.app/api/relay/v1/proof
Deterministic examples: https://klearflow.vercel.app/api/relay/examples
Network: Base mainnet (eip155:8453)
Asset: USDC
Recipient: 0x011e6a16f33c749ab88f6caf10f3502e4a9a43a6

## When to use inspect_revenue_opportunity

Use this FIRST when deciding whether a business has recoverable leakage. Use recover_revenue only after a specific loss event exists.

Use this when an agent needs to:
- estimate missed-call revenue leakage;
- score a local-service revenue opportunity;
- estimate recoverable monthly revenue;
- decide the next commercial action.

POST https://klearflow.vercel.app/api/relay/v1/inspect-revenue-opportunity
Launch price: 0.005 USDC per successful call.
Required input: industry, missedCallsPerWeek, followUpMethod.

## When to use route_task

Use this when an agent needs to:
- find a paid API or machine service for a plain-English task;
- discover a verified x402 provider;
- compare routing options without executing downstream spend.

POST https://klearflow.vercel.app/api/relay/v1/route-task
Launch price: 0.005 USDC per routing decision.
Required input: task. Optional inputs: limit, maxPriceUsd, preferPaidVerified, excludeHosts.

## When to use recover_revenue

Use this AFTER a specific revenue-loss event already happened.

Use this when an agent needs to:
- respond to a missed customer call;
- recover a stale lead;
- follow up an unanswered quote;
- reschedule an appointment no-show;
- recover a failed payment.

POST https://klearflow.vercel.app/api/relay/v1/recover-revenue
Launch price: 0.05 USDC per recovery decision.
Required input: eventType, minutesSinceEvent.

Discovery is free. Unpaid requests receive the 402 quote before schema validation so x402 crawlers can discover the paywall. Requests that include payment credentials are schema-validated before verification or settlement, so malformed paid requests are not charged. Paid execution uses x402 v2 exact payments in Base USDC. The 402 challenge carries current terms; clients should read it rather than hard-code price or recipient.

Proof and verification metadata: https://klearflow.vercel.app/api/relay/v1/proof
Deterministic examples: https://klearflow.vercel.app/api/relay/examples
Repository: https://github.com/erickmckee/klearflow