Discover

Search for data endpoints (deprecated)

Semantic search over the endpoint catalog: registry kNN retrieval, signal-based reranking, relevance floors, and per-result pricing. DEPRECATED in favor of POST /v1/discover/endpoints (same pipeline, card response shape, larger page cap); kept for existing CLI/MCP callers and removed in a future release.

post/v1/discover

Request body

querystring required

Natural-language search query for data endpoints.

limitinteger

Requested result count. A config-driven server-side cap (service.discover.max_results) applies.

minScorenumber

Per-call override for the post-rerank score floor. Results scoring below this are filtered out before truncation to limit. Falls back to the configured default when omitted.

includeUnavailableboolean

Endpoints currently in outage are hidden by default (the page is back-filled from the next ranked candidates). Set true to include them — marked metrics.status: "outage" and ranked last.

supportsX402boolean

Filter by static eligibility for x402 payment (POST /x402/v1/run): true keeps only payable endpoints, false only non-payable ones. Omit for all endpoints. Network availability and request/payment validation are checked at execution time.

x402Networkstring

Narrow to endpoints payable via x402 on this customer-payment network (CAIP-2 id, e.g. eip155:8453). Implies supportsX402=true; an unknown/unconfigured id returns an empty page.

readonlyboolean

Filter by whether running the endpoint can change your workspace resources (phone numbers, files, asset libraries): true keeps only endpoints that cannot create, modify or delete them, false only endpoints that can. Omit for all endpoints. This describes RESOURCE effects only — a readonly endpoint may still perform real-world actions and is still billed.

effectsstring[]

Keep only endpoints whose run can have AT LEAST ONE of the named effects on your workspace resources (phone numbers, files, asset libraries): creates, updates, deletes. Omit for all endpoints. Takes precedence over readonly (readonly=true is the alias for "no write effects"). Resource effects only — an endpoint with no effect may still perform real-world actions and is still billed.

Example request

{
  "query": "twitter posts",
  "limit": 5,
  "minScore": 0.2,
  "x402Network": "eip155:8453",
  "effects": [
    "creates",
    "deletes"
  ]
}

Response

Ranked endpoint recommendations

querystring required
countnumber required

Example response

{
  "results": [
    {
      "provider": "exa",
      "endpoint": "/search"
    }
  ]
}

Changes