Skip to main content
Glama

Find live x402 endpoints

settled_find_endpoints
Read-onlyIdempotent

Free up to 50 calls/day per client (a pass allows 1,000). Live endpoints matching every word of q (in the URL, name, tags or description), best match first, then by quality, price, latency or payers; filter by network and max price; each with payability and delivery verification. Use when: you need an x402 endpoint for a capability and want candidates that are live, payable and, where possible, proven to deliver. Not for: verifying one known URL (settled_check). After: run settled_check or settled_preflight on the one you pick before paying.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "settled_find_endpoints"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoOne to four words every result must match in its URL, name, tags or description, e.g. weather forecast or gift cards; filler words (api, x402, endpoint) are ignored
passNoSettled day pass token: lifts the free daily cap; or send it as the x-settled-pass header
sortNoOrder of results: quality (default), price, latency or payers
limitNoHow many endpoints to return, 1-50 (default 20)
statusNoOnly endpoints with this status; live (default) or any for every status
networkNoOnly endpoints on this network, as a CAIP-2 id, e.g. eip155:8453 for Base
max_priceNoHighest price per call in USD, e.g. 0.01
payer_tokenNoA Settled payer token (x4t_…, from POST /x401/token with your payer record): the free tier then follows your wallet, 300 a day, through any gateway

Output Schema

NameRequiredDescriptionDefault
countNoNumber of endpoints returned
errorNoPresent only when the call failed or needs another step: an error code such as pass_required, next to the fields that explain it
itemsNoRanked endpoints, each with payability and delivery status
filtersNoThe filters applied
attestationNoEIP-191 signature over the answer; verify it with settled_verify or any EVM library
attested_atNoWhen Settled signed this answer (ISO 8601)
generated_atNoWhen this list was built

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / q / description
      Previous value: -"Keywords to match in endpoint names, descriptions and URLs, e.g. weather or gift cards"New value: +"One to four words every result must match in its URL, name, tags or description, e.g. weather forecast or gift cards; filler words (api, x402, endpoint) are ignored"
  2. Changed1 schema field changed
    • addedInput schema / properties / payer_token
      Added value: +{
      +  "description": "A Settled payer token (x4t_…, from POST /x401/token with your payer record): the free tier then follows your wallet, 300 a day, through any gateway",
      +  "type": "string"
      +}
  3. Changed3 schema fields changed
    • addedInput schema / properties / max_price / minimum
      Added value: +0
    • changedInput schema / properties / status / description
      Previous value: -"Endpoint status: live (default), degraded, dead, free, auth_gated, not_found, quote_invalid, unknown or any"New value: +"Only endpoints with this status; live (default) or any for every status"
    • addedInput schema / properties / status / enum
      Added value: +[
      +  "live",
      +  "degraded",
      +  "dead",
      +  "free",
      +  "auth_gated",
      +  "not_found",
      +  "quote_invalid",
      +  "unknown",
      +  "any"
      +]
  4. First observed

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare read-only, idempotent and non-destructive; the description goes well beyond them by disclosing quota tiers (free 50/day per client, 1,000 with a pass, 300/day per wallet with a payer token), result ordering, and that results carry payability and delivery verification signals.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core capability and quota, then structured with clear 'Use when' / 'Not for' / 'After' markers. Dense and slightly run-on in the first sentence, but essentially every clause carries actionable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter discovery tool with an output schema, the description covers scope, filtering, ordering, quota/auth mechanics, and the correct workflow around it. An agent has everything needed to select and call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the heavy lifting is already done; the description mainly restates the schema (all-word matching on q, sort order, network and max-price filters, pass lifting the cap). It adds no syntax or edge-case detail beyond what the parameter descriptions provide, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — finding live x402 endpoints matching every word of q — plus ranking and filters. Explicitly separates itself from settled_check (verifying one known URL), so an agent can route without inspecting schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides an explicit 'Use when' condition (need an endpoint for a capability, want live/payable/proven candidates), a 'Not for' exclusion naming the sibling to use instead, and a follow-up step ('After: run settled_check or settled_preflight'). Nothing is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources