We buy from x402 endpoints with real USDC and publish delivery outcomes. Check before you spend.
Search a registry of paid (x402) APIs and datasets verified by real paid purchases — nohumans pays listed endpoints real USDC and confirms delivery. Returns ranked results: verified listings first, then by reputation score (0..1, recency-weighted probe success), then by ascending price. Each result includes has_sample (boolean) — true means you can cheaply test real output before paying full price; prefer these when a listing is new or thinly-reputed and you can't yet judge it from score alone. Use this before spending money to find services that actually work. Prefer results with status 'verified' and score >= 0.8. Zero results means no known service matches — do not invent endpoints. Always describe the actual need in query in your own words — what data, what freshness, what format, what constraint prompted the search — rather than only setting category/max_price/min_score filters. The exact wording of what you're looking for is what improves this directory over time; a bare filter with no query text tells us far less about what was actually needed.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum results to return (default 10, cap 50). | |
| query | No | Describe what you actually need, in your own words and as specifically as possible — not just a topic, but the real constraint: e.g. 'sub-second latency wallet risk scoring for Base memecoins', 'EUR/USD spot rate with sub-100ms freshness', 'translate legal contracts, not casual text'. This text is what makes results relevant and is the only place that level of detail is captured — category and price are coarse filters on top of it, not a substitute for it. Only leave this empty if you are genuinely just browsing with no specific need in mind. | |
| category | No | One of the 40 most-populated existing categories, most-used first. Omit and rely on free-text `query` instead if none fit well — an unmatched or long-tail category still works via text-search fallback, it just won't be offered here as a constrained choice. | |
| max_price | No | Maximum per-call price. Omit for no cap. | |
| min_score | No | Minimum reputation score, 0..1. Use 0.8 to only see reliably-passing services. |
| Name | Required | Description |
|---|---|---|
| count | Yes | |
| results | Yes | |
| category_expanded | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds substantial behavior beyond that: exact ranking order (verified first, then reputation score, then ascending price), the meaning of has_sample, and a zero-results rule: 'do not invent endpoints.' This is strong, non-obvious behavioral disclosure.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is longer than average but well-structured and front-loaded with purpose, then ranking, then usage guidance. Every sentence contributes either ranking semantics, query guidance, or decision rules. It is slightly repetitive around the importance of `query`, but not wasteful enough to drop to a 3.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has an output schema and read-only/idempotent annotations, the description covers what matters for correct invocation: how results are ranked, how to interpret has_sample, what score threshold to prefer, how to handle zero results, and how to write an effective `query`. Nothing essential for calling this tool is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3. The tool description adds meaning beyond the schema by explaining that score is 'recency-weighted probe success', that has_sample enables cheap testing, and by strongly instructing agents to populate `query` with actual need rather than relying only on filters. This adds value, though the schema already covers the basic semantics of each parameter.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: 'Search a registry of paid (x402) APIs and datasets verified by real paid purchases.' This clearly differentiates find_paid_service from the sibling tools get_service_details and resolve_endpoint, which are about inspecting a known service rather than discovering one.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives explicit when-to-use guidance: 'Use this before spending money to find services that actually work,' and gives decision rules like preferring 'verified' and score >= 0.8, and using has_sample for thinly-reputed listings. It does not explicitly name sibling tools as alternatives or state when not to use this tool, so it falls just short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Fetch the full record for one listing by id (from find_paid_service results), led by paid_verification — whether nohumans has paid this endpoint real USDC and confirmed delivery, with the settlement tx hash as on-chain proof where settled — plus endpoint URL, request/response JSON Schemas when provided, accepted chains, pricing, and reputation detail (probe count, last successful probe, consecutive failures). Call this before making a paid request so you know the exact request shape, current reliability, and whether real-money delivery has been independently confirmed.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Listing id, as returned by find_paid_service. |
| Name | Required | Description |
|---|---|---|
| id | Yes | |
| kind | No | |
| name | Yes | |
| score | No | |
| chains | No | |
| status | Yes | |
| category | No | |
| transport | No | |
| has_sample | No | |
| kind_notes | No | |
| obs_pay_to | No | |
| obs_scheme | No | |
| payto_note | No | |
| description | No | |
| obs_network | No | |
| probe_count | No | |
| endpoint_url | Yes | |
| price_amount | Yes | |
| report_count | No | |
| report_score | No | |
| sample_query | No | |
| x402_version | No | |
| evidence_note | No | |
| evidence_tier | No | |
| onchain_daily | No | |
| onchain_shape | No | |
| paid_verified | No | |
| response_mime | No | |
| last_probed_at | No | |
| p50_latency_ms | No | |
| p95_latency_ms | No | |
| p99_latency_ms | No | |
| payto_unstable | No | |
| price_currency | No | |
| request_schema | No | |
| distinct_payers | No | |
| response_schema | No | |
| observed_network | No | |
| paid_verification | No | |
| status_changed_at | No | |
| verdict_age_seconds | No | |
| payto_distinct_recent | No | |
| onchain_unique_payers_30d | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds meaningful context beyond that: the paid_verification semantics (real USDC payment with settlement tx hash as on-chain proof where settled) and the reputation fields an agent can use to gauge reliability before spending money. No contradiction with annotations, and the added context is decision-relevant rather than padding.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The core purpose is front-loaded ('Fetch the full record for one listing by id'), and the second sentence delivers the usage guidance cleanly. The first sentence is long and dense (~70 words), but every clause earns its place: fields, verification semantics, and reliability signals all matter to an agent deciding whether to risk real money. Slightly long, but justified by the stakes.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's low complexity (one parameter, read-only, idempotent), the description is complete: it states what is returned, where the id comes from, when to call it, and what the paid_verification proof means. An output schema exists so return-value details are covered structurally, and annotations handle the safety profile. Nothing an agent needs to decide whether to invoke this before a paid request is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% — the single id parameter is already documented as 'Listing id, as returned by find_paid_service.' The tool description largely repeats this provenance ('from find_paid_service results') rather than adding new meaning. Baseline 3 is appropriate since the schema carries the full parameter burden and the description adds nothing beyond reinforcement.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific verb and resource — 'Fetch the full record for one listing by id' — and immediately scopes it with provenance ('from find_paid_service results'), distinguishing it from its siblings. It enumerates the record's contents (paid_verification, endpoint URL, JSON schemas, chains, pricing, reputation), so an agent knows exactly what this tool returns and how it differs from find_paid_service and resolve_endpoint.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives explicit when-to-use guidance: 'Call this before making a paid request so you know the exact request shape, current reliability, and whether real-money delivery has been independently confirmed.' It also implies the workflow sequence (find_paid_service results feed the id here), which orients the agent. It stops short of stating when-not-to-use or naming alternatives as exclusions, so it misses a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Pre-spend verdict on an endpoint URL you already hold — from another catalog, a prompt, a config, anywhere: check before paying instead of buying to find out. Returns match 'active' with the same full record as get_service_details (status, reputation score, paid_verification with on-chain tx proof, observed 402 protocol detail), match 'delisted' if the endpoint was listed here and later removed (treat as a warning), or a not-listed result. IMPORTANT: not-listed means never checked here, NOT unsafe — absence of a record is not a verdict either way. Use this as the pre-spend check when you have a URL in hand and no listing id; use find_paid_service instead when you have a need but no URL.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The endpoint URL exactly as you hold it, including any query string (parameterized listings bake params into the URL, so the query string matters). Trailing slashes and http/https differences are tolerated. |
| Name | Required | Description |
|---|---|---|
| note | No | |
| match | Yes | |
| detail | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description goes well beyond the readOnly/openWorld/idempotent annotations. It explains the three possible outcomes ('active', 'delisted', not-listed), warns that delisted should be treated as a warning, and emphasizes that an absence of a record is not a safety verdict. This is exactly the kind of nuanced behavioral context an agent needs.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is front-loaded with the core purpose and then efficiently covers return variants, the critical not-listed caveat, and explicit usage routing. Each sentence earns its place; there is no repetition or filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description is complete for selection and invocation: it explains when to use the tool, what the outcome variants mean, how to interpret a not-listed result, and the parameter schema fully documents the URL format. Combined with strong annotations and an output schema, nothing critical is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already provides 100% coverage for the single url parameter, including exact-match guidance, query-string significance, and tolerance for trailing slashes and http/https differences. The description adds source context ('from another catalog, a prompt, a config') but does not fundamentally extend the parameter semantics beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with a clear and specific purpose: 'Pre-spend verdict on an endpoint URL you already hold.' It distinguishes itself from siblings by framing the use case as having a URL but no listing id, and explicitly contrasts with find_paid_service for need-without-URL scenarios.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives explicit usage guidance: use this tool as the pre-spend check when you have a URL in hand and no listing id, and use find_paid_service instead when you have a need but no URL. It also clarifies the meaning of the not-listed outcome, preventing a likely misinterpretation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
find_paid_service1 field changedInput schema / properties / category / enumPrevious value: -[
- "data.misc",
- "data.crypto",
- "data.stocks",
- "data.search",
- "data.defi",
- "data.intelligence",
- "infra.utility",
- "data.macro",
- "data.fx",
- "data.enrichment",
- "infra.inference",
- "data.derivatives",
- "data.social",
- "data.weather",
- "infra.trust",
- "infra.validation",
- "infra.scraping",
- "data.onchain",
- "verification",
- "data.reference",
- "data.security",
- "infra.security",
- "compute.utility",
- "data.energy",
- "data.health",
- "infra.creative",
- "data.research",
- "compute.nlp",
- "crypto.token-safety",
- "data.utility",
- "commerce.general",
- "infra.compliance",
- "infra.payments",
- "infra.search",
- "data.validation",
- "data.x402",
- "infra.media",
- "commerce.giftcards",
- "data.gaming",
- "infra.compute"
-]New value: +[
+ "data.other",
+ "data.crypto",
+ "data.misc",
+ "data.web",
+ "data.weather",
+ "data.markets",
+ "compute.llm",
+ "compute.media",
+ "data.geo",
+ "data.fx",
+ "data.stocks",
+ "compute.tools",
+ "data.search",
+ "data.defi",
+ "data.intelligence",
+ "data.news",
+ "infra.utility",
+ "data.macro",
+ "data.contacts",
+ "data.enrichment",
+ "infra.inference",
+ "data.derivatives",
+ "data.social",
+ "infra.trust",
+ "infra.validation",
+ "infra.scraping",
+ "data.onchain",
+ "verification",
+ "data.reference",
+ "data.security",
+ "infra.security",
+ "compute.utility",
+ "data.energy",
+ "data.health",
+ "infra.creative",
+ "data.research",
+ "compute.nlp",
+ "crypto.token-safety",
+ "data.utility",
+ "commerce.general"
+]find_paid_service1 field changedInput schema / properties / category / enumPrevious value: -[
- "data.misc",
- "data.crypto",
- "data.stocks",
- "data.search",
- "data.defi",
- "data.intelligence",
- "infra.utility",
- "data.macro",
- "data.fx",
- "data.enrichment",
- "infra.inference",
- "data.derivatives",
- "data.social",
- "data.weather",
- "infra.trust",
- "infra.validation",
- "infra.scraping",
- "data.onchain",
- "verification",
- "data.reference",
- "data.security",
- "infra.security",
- "compute.utility",
- "data.energy",
- "data.health",
- "infra.creative",
- "data.research",
- "compute.nlp",
- "crypto.token-safety",
- "commerce.general",
- "data.utility",
- "infra.compliance",
- "infra.payments",
- "infra.search",
- "data.validation",
- "data.x402",
- "infra.media",
- "commerce.giftcards",
- "data.gaming",
- "infra.compute"
-]New value: +[
+ "data.misc",
+ "data.crypto",
+ "data.stocks",
+ "data.search",
+ "data.defi",
+ "data.intelligence",
+ "infra.utility",
+ "data.macro",
+ "data.fx",
+ "data.enrichment",
+ "infra.inference",
+ "data.derivatives",
+ "data.social",
+ "data.weather",
+ "infra.trust",
+ "infra.validation",
+ "infra.scraping",
+ "data.onchain",
+ "verification",
+ "data.reference",
+ "data.security",
+ "infra.security",
+ "compute.utility",
+ "data.energy",
+ "data.health",
+ "infra.creative",
+ "data.research",
+ "compute.nlp",
+ "crypto.token-safety",
+ "data.utility",
+ "commerce.general",
+ "infra.compliance",
+ "infra.payments",
+ "infra.search",
+ "data.validation",
+ "data.x402",
+ "infra.media",
+ "commerce.giftcards",
+ "data.gaming",
+ "infra.compute"
+]find_paid_service1 field changedInput schema / properties / category / enumPrevious value: -[
- "data.misc",
- "data.crypto",
- "data.stocks",
- "data.search",
- "data.defi",
- "data.intelligence",
- "infra.utility",
- "data.macro",
- "data.fx",
- "infra.inference",
- "data.enrichment",
- "data.derivatives",
- "data.social",
- "data.weather",
- "infra.trust",
- "infra.validation",
- "infra.scraping",
- "data.onchain",
- "verification",
- "data.reference",
- "data.security",
- "infra.security",
- "compute.utility",
- "data.energy",
- "data.health",
- "infra.creative",
- "data.research",
- "compute.nlp",
- "crypto.token-safety",
- "commerce.general",
- "data.utility",
- "infra.compliance",
- "infra.payments",
- "infra.search",
- "data.validation",
- "data.x402",
- "infra.media",
- "commerce.giftcards",
- "data.gaming",
- "infra.compute"
-]New value: +[
+ "data.misc",
+ "data.crypto",
+ "data.stocks",
+ "data.search",
+ "data.defi",
+ "data.intelligence",
+ "infra.utility",
+ "data.macro",
+ "data.fx",
+ "data.enrichment",
+ "infra.inference",
+ "data.derivatives",
+ "data.social",
+ "data.weather",
+ "infra.trust",
+ "infra.validation",
+ "infra.scraping",
+ "data.onchain",
+ "verification",
+ "data.reference",
+ "data.security",
+ "infra.security",
+ "compute.utility",
+ "data.energy",
+ "data.health",
+ "infra.creative",
+ "data.research",
+ "compute.nlp",
+ "crypto.token-safety",
+ "commerce.general",
+ "data.utility",
+ "infra.compliance",
+ "infra.payments",
+ "infra.search",
+ "data.validation",
+ "data.x402",
+ "infra.media",
+ "commerce.giftcards",
+ "data.gaming",
+ "infra.compute"
+]find_paid_service1 field changedInput schema / properties / category / enumPrevious value: -[
- "data.misc",
- "data.crypto",
- "data.stocks",
- "data.search",
- "data.defi",
- "data.intelligence",
- "infra.utility",
- "data.macro",
- "data.fx",
- "infra.inference",
- "data.enrichment",
- "data.derivatives",
- "data.social",
- "data.weather",
- "infra.trust",
- "infra.validation",
- "infra.scraping",
- "data.onchain",
- "verification",
- "data.reference",
- "data.security",
- "infra.security",
- "compute.utility",
- "data.energy",
- "data.health",
- "infra.creative",
- "data.research",
- "compute.nlp",
- "crypto.token-safety",
- "commerce.general",
- "data.utility",
- "infra.compliance",
- "infra.payments",
- "infra.search",
- "data.validation",
- "data.x402",
- "commerce.giftcards",
- "data.gaming",
- "infra.compute",
- "infra.mcp"
-]New value: +[
+ "data.misc",
+ "data.crypto",
+ "data.stocks",
+ "data.search",
+ "data.defi",
+ "data.intelligence",
+ "infra.utility",
+ "data.macro",
+ "data.fx",
+ "infra.inference",
+ "data.enrichment",
+ "data.derivatives",
+ "data.social",
+ "data.weather",
+ "infra.trust",
+ "infra.validation",
+ "infra.scraping",
+ "data.onchain",
+ "verification",
+ "data.reference",
+ "data.security",
+ "infra.security",
+ "compute.utility",
+ "data.energy",
+ "data.health",
+ "infra.creative",
+ "data.research",
+ "compute.nlp",
+ "crypto.token-safety",
+ "commerce.general",
+ "data.utility",
+ "infra.compliance",
+ "infra.payments",
+ "infra.search",
+ "data.validation",
+ "data.x402",
+ "infra.media",
+ "commerce.giftcards",
+ "data.gaming",
+ "infra.compute"
+]find_paid_service1 field changedInput schema / properties / category / enumPrevious value: -[
- "data.misc",
- "data.crypto",
- "data.stocks",
- "data.search",
- "data.defi",
- "data.intelligence",
- "infra.utility",
- "data.macro",
- "data.fx",
- "infra.inference",
- "data.enrichment",
- "data.derivatives",
- "data.social",
- "data.weather",
- "infra.trust",
- "infra.validation",
- "infra.scraping",
- "data.health",
- "data.onchain",
- "infra.security",
- "verification",
- "data.reference",
- "data.security",
- "compute.utility",
- "data.energy",
- "infra.creative",
- "crypto.token-safety",
- "data.research",
- "compute.nlp",
- "commerce.general",
- "data.utility",
- "infra.compliance",
- "infra.payments",
- "infra.search",
- "data.validation",
- "data.x402",
- "commerce.giftcards",
- "data.gaming",
- "infra.compute",
- "infra.mcp"
-]New value: +[
+ "data.misc",
+ "data.crypto",
+ "data.stocks",
+ "data.search",
+ "data.defi",
+ "data.intelligence",
+ "infra.utility",
+ "data.macro",
+ "data.fx",
+ "infra.inference",
+ "data.enrichment",
+ "data.derivatives",
+ "data.social",
+ "data.weather",
+ "infra.trust",
+ "infra.validation",
+ "infra.scraping",
+ "data.onchain",
+ "verification",
+ "data.reference",
+ "data.security",
+ "infra.security",
+ "compute.utility",
+ "data.energy",
+ "data.health",
+ "infra.creative",
+ "data.research",
+ "compute.nlp",
+ "crypto.token-safety",
+ "commerce.general",
+ "data.utility",
+ "infra.compliance",
+ "infra.payments",
+ "infra.search",
+ "data.validation",
+ "data.x402",
+ "commerce.giftcards",
+ "data.gaming",
+ "infra.compute",
+ "infra.mcp"
+]find_paid_service1 field changedInput schema / properties / category / enumPrevious value: -[
- "data.misc",
- "data.crypto",
- "data.stocks",
- "data.search",
- "data.defi",
- "data.intelligence",
- "infra.utility",
- "data.macro",
- "data.fx",
- "data.enrichment",
- "infra.inference",
- "data.derivatives",
- "data.social",
- "data.weather",
- "infra.trust",
- "infra.validation",
- "infra.scraping",
- "data.health",
- "data.onchain",
- "infra.security",
- "verification",
- "data.reference",
- "data.security",
- "compute.utility",
- "data.energy",
- "infra.creative",
- "crypto.token-safety",
- "data.research",
- "compute.nlp",
- "commerce.general",
- "data.utility",
- "infra.compliance",
- "infra.payments",
- "data.validation",
- "data.x402",
- "commerce.giftcards",
- "data.gaming",
- "infra.mcp",
- "ai.text",
- "compute.rendering"
-]New value: +[
+ "data.misc",
+ "data.crypto",
+ "data.stocks",
+ "data.search",
+ "data.defi",
+ "data.intelligence",
+ "infra.utility",
+ "data.macro",
+ "data.fx",
+ "infra.inference",
+ "data.enrichment",
+ "data.derivatives",
+ "data.social",
+ "data.weather",
+ "infra.trust",
+ "infra.validation",
+ "infra.scraping",
+ "data.health",
+ "data.onchain",
+ "infra.security",
+ "verification",
+ "data.reference",
+ "data.security",
+ "compute.utility",
+ "data.energy",
+ "infra.creative",
+ "crypto.token-safety",
+ "data.research",
+ "compute.nlp",
+ "commerce.general",
+ "data.utility",
+ "infra.compliance",
+ "infra.payments",
+ "infra.search",
+ "data.validation",
+ "data.x402",
+ "commerce.giftcards",
+ "data.gaming",
+ "infra.compute",
+ "infra.mcp"
+]find_paid_service1 field changedInput schema / properties / category / enumPrevious value: -[
- "data.misc",
- "data.crypto",
- "data.stocks",
- "data.search",
- "data.defi",
- "data.intelligence",
- "infra.utility",
- "data.macro",
- "data.fx",
- "data.enrichment",
- "infra.inference",
- "data.derivatives",
- "data.social",
- "data.weather",
- "infra.trust",
- "infra.validation",
- "infra.scraping",
- "data.health",
- "data.onchain",
- "infra.security",
- "data.reference",
- "data.security",
- "compute.utility",
- "data.energy",
- "infra.creative",
- "crypto.token-safety",
- "data.research",
- "compute.nlp",
- "commerce.general",
- "data.utility",
- "infra.compliance",
- "infra.payments",
- "verification",
- "data.validation",
- "data.x402",
- "commerce.giftcards",
- "data.gaming",
- "infra.mcp",
- "ai.text",
- "compute.rendering"
-]New value: +[
+ "data.misc",
+ "data.crypto",
+ "data.stocks",
+ "data.search",
+ "data.defi",
+ "data.intelligence",
+ "infra.utility",
+ "data.macro",
+ "data.fx",
+ "data.enrichment",
+ "infra.inference",
+ "data.derivatives",
+ "data.social",
+ "data.weather",
+ "infra.trust",
+ "infra.validation",
+ "infra.scraping",
+ "data.health",
+ "data.onchain",
+ "infra.security",
+ "verification",
+ "data.reference",
+ "data.security",
+ "compute.utility",
+ "data.energy",
+ "infra.creative",
+ "crypto.token-safety",
+ "data.research",
+ "compute.nlp",
+ "commerce.general",
+ "data.utility",
+ "infra.compliance",
+ "infra.payments",
+ "data.validation",
+ "data.x402",
+ "commerce.giftcards",
+ "data.gaming",
+ "infra.mcp",
+ "ai.text",
+ "compute.rendering"
+]get_service_details29 fields changedOutput schema / properties / categoryAdded value: +{
+ "type": "string"
+}Output schema / properties / chainsAdded value: +{
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+}Output schema / properties / descriptionAdded value: +{
+ "type": "string"
+}Output schema / properties / distinct_payersAdded value: +{
+ "type": [
+ "integer",
+ "null"
+ ]
+}Output schema / properties / endpoint_urlAdded value: +{
+ "type": "string"
+}Output schema / properties / evidence_noteAdded value: +{
+ "type": [
+ "string",
+ "null"
+ ]
+}Output schema / properties / evidence_tierAdded value: +{
+ "type": "string"
+}Output schema / properties / has_sampleAdded value: +{
+ "type": "boolean"
+}Output schema / properties / idAdded value: +{
+ "type": "string"
+}Output schema / properties / kindAdded value: +{
+ "enum": [
+ "api",
+ "agent"
+ ],
+ "type": "string"
+}Output schema / properties / last_probed_atAdded value: +{
+ "type": [
+ "integer",
+ "null"
+ ]
+}Output schema / properties / nameAdded value: +{
+ "type": "string"
+}Output schema / properties / observed_networkAdded value: +{
+ "type": [
+ "string",
+ "null"
+ ]
+}Output schema / properties / onchain_unique_payers_30dAdded value: +{
+ "type": [
+ "integer",
+ "null"
+ ]
+}Output schema / properties / p50_latency_msAdded value: +{
+ "type": [
+ "number",
+ "null"
+ ]
+}Output schema / properties / p95_latency_msAdded value: +{
+ "type": [
+ "integer",
+ "null"
+ ]
+}Output schema / properties / p99_latency_msAdded value: +{
+ "type": [
+ "integer",
+ "null"
+ ]
+}Output schema / properties / paid_verifiedAdded value: +{
+ "type": "boolean"
+}Output schema / properties / price_amountAdded value: +{
+ "type": "number"
+}Output schema / properties / price_currencyAdded value: +{
+ "type": "string"
+}Output schema / properties / probe_countAdded value: +{
+ "type": [
+ "integer",
+ "null"
+ ]
+}Output schema / properties / report_countAdded value: +{
+ "type": [
+ "integer",
+ "null"
+ ]
+}Output schema / properties / report_scoreAdded value: +{
+ "type": [
+ "number",
+ "null"
+ ]
+}Output schema / properties / response_mimeAdded value: +{
+ "type": [
+ "string",
+ "null"
+ ]
+}Output schema / properties / scoreAdded value: +{
+ "type": [
+ "number",
+ "null"
+ ]
+}Output schema / properties / statusAdded value: +{
+ "enum": [
+ "verified",
+ "unverified",
+ "failing"
+ ],
+ "type": "string"
+}Output schema / properties / status_changed_atAdded value: +{
+ "type": [
+ "integer",
+ "null"
+ ]
+}Output schema / properties / verdict_age_secondsAdded value: +{
+ "type": [
+ "integer",
+ "null"
+ ]
+}Output schema / properties / x402_versionAdded value: +{
+ "type": [
+ "integer",
+ "null"
+ ]
+}find_paid_service1 field changedInput schema / properties / category / enumPrevious value: -[
- "data.misc",
- "data.crypto",
- "data.stocks",
- "data.search",
- "data.defi",
- "data.intelligence",
- "infra.utility",
- "data.macro",
- "data.fx",
- "data.enrichment",
- "infra.inference",
- "data.derivatives",
- "data.social",
- "data.weather",
- "infra.trust",
- "infra.validation",
- "infra.scraping",
- "data.health",
- "data.onchain",
- "infra.security",
- "data.reference",
- "data.security",
- "compute.utility",
- "data.energy",
- "infra.creative",
- "crypto.token-safety",
- "data.research",
- "compute.nlp",
- "commerce.general",
- "data.utility",
- "infra.compliance",
- "verification",
- "data.validation",
- "data.x402",
- "infra.payments",
- "commerce.giftcards",
- "data.gaming",
- "infra.mcp",
- "ai.text",
- "compute.rendering"
-]New value: +[
+ "data.misc",
+ "data.crypto",
+ "data.stocks",
+ "data.search",
+ "data.defi",
+ "data.intelligence",
+ "infra.utility",
+ "data.macro",
+ "data.fx",
+ "data.enrichment",
+ "infra.inference",
+ "data.derivatives",
+ "data.social",
+ "data.weather",
+ "infra.trust",
+ "infra.validation",
+ "infra.scraping",
+ "data.health",
+ "data.onchain",
+ "infra.security",
+ "data.reference",
+ "data.security",
+ "compute.utility",
+ "data.energy",
+ "infra.creative",
+ "crypto.token-safety",
+ "data.research",
+ "compute.nlp",
+ "commerce.general",
+ "data.utility",
+ "infra.compliance",
+ "infra.payments",
+ "verification",
+ "data.validation",
+ "data.x402",
+ "commerce.giftcards",
+ "data.gaming",
+ "infra.mcp",
+ "ai.text",
+ "compute.rendering"
+]find_paid_service1 field changedOutput schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": true,
+ "properties": {
+ "category_expanded": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "count": {
+ "type": "integer"
+ },
+ "results": {
+ "items": {
+ "additionalProperties": true,
+ "properties": {
+ "category": {
+ "type": "string"
+ },
+ "chains": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "description": {
+ "type": "string"
+ },
+ "distinct_payers": {
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
+ "endpoint_url": {
+ "type": "string"
+ },
+ "evidence_note": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "evidence_tier": {
+ "type": "string"
+ },
+ "has_sample": {
+ "type": "boolean"
+ },
+ "id": {
+ "type": "string"
+ },
+ "kind": {
+ "enum": [
+ "api",
+ "agent"
+ ],
+ "type": "string"
+ },
+ "last_probed_at": {
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
+ "name": {
+ "type": "string"
+ },
+ "observed_network": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "onchain_unique_payers_30d": {
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
+ "p50_latency_ms": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "p95_latency_ms": {
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
+ "p99_latency_ms": {
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
+ "paid_verified": {
+ "type": "boolean"
+ },
+ "price_amount": {
+ "type": "number"
+ },
+ "price_currency": {
+ "type": "string"
+ },
+ "probe_count": {
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
+ "report_count": {
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
+ "report_score": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "response_mime": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "score": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "status": {
+ "enum": [
+ "verified",
+ "unverified",
+ "failing"
+ ],
+ "type": "string"
+ },
+ "status_changed_at": {
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
+ "verdict_age_seconds": {
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
+ "x402_version": {
+ "type": [
+ "integer",
+ "null"
+ ]
+ }
+ },
+ "required": [
+ "id",
+ "name",
+ "endpoint_url",
+ "status",
+ "price_amount"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "count",
+ "results"
+ ],
+ "type": "object"
+}get_service_details1 field changedOutput schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": true,
+ "properties": {
+ "kind_notes": {
+ "additionalProperties": true,
+ "type": [
+ "object",
+ "null"
+ ]
+ },
+ "obs_network": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "obs_pay_to": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "obs_scheme": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "onchain_daily": {
+ "items": {
+ "additionalProperties": true,
+ "type": "object"
+ },
+ "type": [
+ "array",
+ "null"
+ ]
+ },
+ "onchain_shape": {
+ "additionalProperties": true,
+ "type": [
+ "object",
+ "null"
+ ]
+ },
+ "paid_verification": {
+ "additionalProperties": true,
+ "type": "object"
+ },
+ "payto_distinct_recent": {
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
+ "payto_note": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "payto_unstable": {
+ "type": "boolean"
+ },
+ "request_schema": {
+ "additionalProperties": true,
+ "type": [
+ "object",
+ "null"
+ ]
+ },
+ "response_schema": {
+ "additionalProperties": true,
+ "type": [
+ "object",
+ "null"
+ ]
+ },
+ "sample_query": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "transport": {
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "required": [
+ "id",
+ "name",
+ "endpoint_url",
+ "status",
+ "price_amount"
+ ],
+ "type": "object"
+}resolve_endpoint1 field changedOutput schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": true,
+ "properties": {
+ "detail": {
+ "additionalProperties": true,
+ "type": [
+ "object",
+ "null"
+ ]
+ },
+ "match": {
+ "enum": [
+ "active",
+ "delisted",
+ "unknown"
+ ],
+ "type": "string"
+ },
+ "note": {
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "required": [
+ "match"
+ ],
+ "type": "object"
+}find_paid_service1 field changedInput schema / properties / category / enumPrevious value: -[
- "data.misc",
- "data.crypto",
- "data.stocks",
- "data.search",
- "data.defi",
- "data.intelligence",
- "infra.utility",
- "data.macro",
- "data.fx",
- "data.enrichment",
- "infra.inference",
- "data.derivatives",
- "data.social",
- "data.weather",
- "infra.trust",
- "infra.validation",
- "infra.scraping",
- "data.health",
- "data.onchain",
- "infra.security",
- "data.security",
- "compute.utility",
- "data.energy",
- "data.reference",
- "infra.creative",
- "crypto.token-safety",
- "data.research",
- "compute.nlp",
- "commerce.general",
- "data.utility",
- "infra.compliance",
- "verification",
- "data.validation",
- "data.x402",
- "infra.payments",
- "commerce.giftcards",
- "data.gaming",
- "infra.mcp",
- "ai.text",
- "compute.rendering"
-]New value: +[
+ "data.misc",
+ "data.crypto",
+ "data.stocks",
+ "data.search",
+ "data.defi",
+ "data.intelligence",
+ "infra.utility",
+ "data.macro",
+ "data.fx",
+ "data.enrichment",
+ "infra.inference",
+ "data.derivatives",
+ "data.social",
+ "data.weather",
+ "infra.trust",
+ "infra.validation",
+ "infra.scraping",
+ "data.health",
+ "data.onchain",
+ "infra.security",
+ "data.reference",
+ "data.security",
+ "compute.utility",
+ "data.energy",
+ "infra.creative",
+ "crypto.token-safety",
+ "data.research",
+ "compute.nlp",
+ "commerce.general",
+ "data.utility",
+ "infra.compliance",
+ "verification",
+ "data.validation",
+ "data.x402",
+ "infra.payments",
+ "commerce.giftcards",
+ "data.gaming",
+ "infra.mcp",
+ "ai.text",
+ "compute.rendering"
+]find_paid_service1 field changedInput schema / properties / category / enumPrevious value: -[
- "data.misc",
- "data.crypto",
- "data.stocks",
- "data.search",
- "data.defi",
- "data.intelligence",
- "infra.utility",
- "data.macro",
- "data.fx",
- "data.enrichment",
- "infra.inference",
- "data.derivatives",
- "data.social",
- "data.weather",
- "infra.trust",
- "infra.validation",
- "infra.scraping",
- "data.health",
- "data.onchain",
- "data.security",
- "infra.security",
- "compute.utility",
- "data.energy",
- "data.reference",
- "infra.creative",
- "crypto.token-safety",
- "data.research",
- "compute.nlp",
- "commerce.general",
- "data.utility",
- "infra.compliance",
- "verification",
- "data.validation",
- "data.x402",
- "infra.payments",
- "commerce.giftcards",
- "data.gaming",
- "infra.mcp",
- "ai.text",
- "compute.rendering"
-]New value: +[
+ "data.misc",
+ "data.crypto",
+ "data.stocks",
+ "data.search",
+ "data.defi",
+ "data.intelligence",
+ "infra.utility",
+ "data.macro",
+ "data.fx",
+ "data.enrichment",
+ "infra.inference",
+ "data.derivatives",
+ "data.social",
+ "data.weather",
+ "infra.trust",
+ "infra.validation",
+ "infra.scraping",
+ "data.health",
+ "data.onchain",
+ "infra.security",
+ "data.security",
+ "compute.utility",
+ "data.energy",
+ "data.reference",
+ "infra.creative",
+ "crypto.token-safety",
+ "data.research",
+ "compute.nlp",
+ "commerce.general",
+ "data.utility",
+ "infra.compliance",
+ "verification",
+ "data.validation",
+ "data.x402",
+ "infra.payments",
+ "commerce.giftcards",
+ "data.gaming",
+ "infra.mcp",
+ "ai.text",
+ "compute.rendering"
+]find_paid_service1 field changedInput schema / properties / category / enumPrevious value: -[
- "data.misc",
- "data.crypto",
- "data.stocks",
- "data.search",
- "data.defi",
- "data.intelligence",
- "infra.utility",
- "data.macro",
- "data.fx",
- "data.enrichment",
- "infra.inference",
- "data.derivatives",
- "data.social",
- "data.weather",
- "infra.trust",
- "infra.validation",
- "infra.scraping",
- "data.health",
- "data.onchain",
- "data.security",
- "infra.security",
- "compute.utility",
- "data.energy",
- "infra.creative",
- "crypto.token-safety",
- "data.research",
- "compute.nlp",
- "data.reference",
- "commerce.general",
- "data.utility",
- "infra.compliance",
- "verification",
- "data.validation",
- "data.x402",
- "infra.payments",
- "commerce.giftcards",
- "data.gaming",
- "infra.mcp",
- "ai.text",
- "compute.rendering"
-]New value: +[
+ "data.misc",
+ "data.crypto",
+ "data.stocks",
+ "data.search",
+ "data.defi",
+ "data.intelligence",
+ "infra.utility",
+ "data.macro",
+ "data.fx",
+ "data.enrichment",
+ "infra.inference",
+ "data.derivatives",
+ "data.social",
+ "data.weather",
+ "infra.trust",
+ "infra.validation",
+ "infra.scraping",
+ "data.health",
+ "data.onchain",
+ "data.security",
+ "infra.security",
+ "compute.utility",
+ "data.energy",
+ "data.reference",
+ "infra.creative",
+ "crypto.token-safety",
+ "data.research",
+ "compute.nlp",
+ "commerce.general",
+ "data.utility",
+ "infra.compliance",
+ "verification",
+ "data.validation",
+ "data.x402",
+ "infra.payments",
+ "commerce.giftcards",
+ "data.gaming",
+ "infra.mcp",
+ "ai.text",
+ "compute.rendering"
+]find_paid_service1 field changedInput schema / properties / category / enumPrevious value: -[
- "data.misc",
- "data.crypto",
- "data.stocks",
- "data.search",
- "data.defi",
- "data.intelligence",
- "infra.utility",
- "data.macro",
- "data.fx",
- "data.enrichment",
- "infra.inference",
- "data.derivatives",
- "data.social",
- "data.weather",
- "infra.trust",
- "infra.validation",
- "infra.scraping",
- "data.health",
- "data.onchain",
- "data.security",
- "infra.security",
- "compute.utility",
- "data.energy",
- "infra.creative",
- "crypto.token-safety",
- "compute.nlp",
- "data.reference",
- "data.research",
- "commerce.general",
- "data.utility",
- "infra.compliance",
- "verification",
- "data.validation",
- "data.x402",
- "infra.payments",
- "commerce.giftcards",
- "data.gaming",
- "infra.mcp",
- "ai.text",
- "compute.rendering"
-]New value: +[
+ "data.misc",
+ "data.crypto",
+ "data.stocks",
+ "data.search",
+ "data.defi",
+ "data.intelligence",
+ "infra.utility",
+ "data.macro",
+ "data.fx",
+ "data.enrichment",
+ "infra.inference",
+ "data.derivatives",
+ "data.social",
+ "data.weather",
+ "infra.trust",
+ "infra.validation",
+ "infra.scraping",
+ "data.health",
+ "data.onchain",
+ "data.security",
+ "infra.security",
+ "compute.utility",
+ "data.energy",
+ "infra.creative",
+ "crypto.token-safety",
+ "data.research",
+ "compute.nlp",
+ "data.reference",
+ "commerce.general",
+ "data.utility",
+ "infra.compliance",
+ "verification",
+ "data.validation",
+ "data.x402",
+ "infra.payments",
+ "commerce.giftcards",
+ "data.gaming",
+ "infra.mcp",
+ "ai.text",
+ "compute.rendering"
+]find_paid_service1 field changedInput schema / properties / category / enumPrevious value: -[
- "data.misc",
- "data.crypto",
- "data.stocks",
- "data.search",
- "data.defi",
- "data.intelligence",
- "infra.utility",
- "data.macro",
- "data.fx",
- "data.enrichment",
- "infra.inference",
- "data.derivatives",
- "data.social",
- "data.weather",
- "infra.trust",
- "infra.validation",
- "infra.scraping",
- "data.health",
- "data.onchain",
- "data.security",
- "infra.security",
- "compute.utility",
- "data.energy",
- "infra.creative",
- "crypto.token-safety",
- "compute.nlp",
- "data.reference",
- "commerce.general",
- "data.research",
- "data.utility",
- "infra.compliance",
- "verification",
- "data.validation",
- "data.x402",
- "infra.payments",
- "commerce.giftcards",
- "data.gaming",
- "infra.mcp",
- "ai.text",
- "compute.rendering"
-]New value: +[
+ "data.misc",
+ "data.crypto",
+ "data.stocks",
+ "data.search",
+ "data.defi",
+ "data.intelligence",
+ "infra.utility",
+ "data.macro",
+ "data.fx",
+ "data.enrichment",
+ "infra.inference",
+ "data.derivatives",
+ "data.social",
+ "data.weather",
+ "infra.trust",
+ "infra.validation",
+ "infra.scraping",
+ "data.health",
+ "data.onchain",
+ "data.security",
+ "infra.security",
+ "compute.utility",
+ "data.energy",
+ "infra.creative",
+ "crypto.token-safety",
+ "compute.nlp",
+ "data.reference",
+ "data.research",
+ "commerce.general",
+ "data.utility",
+ "infra.compliance",
+ "verification",
+ "data.validation",
+ "data.x402",
+ "infra.payments",
+ "commerce.giftcards",
+ "data.gaming",
+ "infra.mcp",
+ "ai.text",
+ "compute.rendering"
+]find_paid_service1 field changedInput schema / properties / category / enumPrevious value: -[
- "data.misc",
- "data.crypto",
- "data.stocks",
- "data.search",
- "data.defi",
- "data.intelligence",
- "infra.utility",
- "data.macro",
- "data.fx",
- "data.enrichment",
- "infra.inference",
- "data.derivatives",
- "data.social",
- "data.weather",
- "infra.trust",
- "infra.validation",
- "infra.scraping",
- "data.health",
- "data.onchain",
- "data.security",
- "infra.security",
- "compute.utility",
- "crypto.token-safety",
- "data.energy",
- "infra.creative",
- "compute.nlp",
- "data.reference",
- "commerce.general",
- "data.research",
- "data.utility",
- "infra.compliance",
- "verification",
- "data.validation",
- "data.x402",
- "infra.payments",
- "commerce.giftcards",
- "data.gaming",
- "infra.mcp",
- "ai.text",
- "compute.rendering"
-]New value: +[
+ "data.misc",
+ "data.crypto",
+ "data.stocks",
+ "data.search",
+ "data.defi",
+ "data.intelligence",
+ "infra.utility",
+ "data.macro",
+ "data.fx",
+ "data.enrichment",
+ "infra.inference",
+ "data.derivatives",
+ "data.social",
+ "data.weather",
+ "infra.trust",
+ "infra.validation",
+ "infra.scraping",
+ "data.health",
+ "data.onchain",
+ "data.security",
+ "infra.security",
+ "compute.utility",
+ "data.energy",
+ "infra.creative",
+ "crypto.token-safety",
+ "compute.nlp",
+ "data.reference",
+ "commerce.general",
+ "data.research",
+ "data.utility",
+ "infra.compliance",
+ "verification",
+ "data.validation",
+ "data.x402",
+ "infra.payments",
+ "commerce.giftcards",
+ "data.gaming",
+ "infra.mcp",
+ "ai.text",
+ "compute.rendering"
+]find_paid_service1 field changedInput schema / properties / category / enumPrevious value: -[
- "data.misc",
- "data.crypto",
- "data.stocks",
- "data.search",
- "data.defi",
- "data.intelligence",
- "infra.utility",
- "data.macro",
- "data.fx",
- "infra.inference",
- "data.enrichment",
- "data.derivatives",
- "data.social",
- "data.weather",
- "infra.trust",
- "infra.validation",
- "infra.scraping",
- "data.health",
- "data.onchain",
- "data.security",
- "infra.security",
- "compute.utility",
- "crypto.token-safety",
- "data.energy",
- "infra.creative",
- "compute.nlp",
- "data.reference",
- "commerce.general",
- "data.research",
- "data.utility",
- "infra.compliance",
- "verification",
- "data.validation",
- "data.x402",
- "infra.payments",
- "commerce.giftcards",
- "data.gaming",
- "infra.mcp",
- "ai.text",
- "compute.rendering"
-]New value: +[
+ "data.misc",
+ "data.crypto",
+ "data.stocks",
+ "data.search",
+ "data.defi",
+ "data.intelligence",
+ "infra.utility",
+ "data.macro",
+ "data.fx",
+ "data.enrichment",
+ "infra.inference",
+ "data.derivatives",
+ "data.social",
+ "data.weather",
+ "infra.trust",
+ "infra.validation",
+ "infra.scraping",
+ "data.health",
+ "data.onchain",
+ "data.security",
+ "infra.security",
+ "compute.utility",
+ "crypto.token-safety",
+ "data.energy",
+ "infra.creative",
+ "compute.nlp",
+ "data.reference",
+ "commerce.general",
+ "data.research",
+ "data.utility",
+ "infra.compliance",
+ "verification",
+ "data.validation",
+ "data.x402",
+ "infra.payments",
+ "commerce.giftcards",
+ "data.gaming",
+ "infra.mcp",
+ "ai.text",
+ "compute.rendering"
+]find_paid_service1 field changedInput schema / properties / category / enumPrevious value: -[
- "data.misc",
- "data.crypto",
- "data.stocks",
- "data.search",
- "data.defi",
- "data.intelligence",
- "infra.utility",
- "data.macro",
- "data.fx",
- "infra.inference",
- "data.enrichment",
- "data.derivatives",
- "data.social",
- "data.weather",
- "infra.trust",
- "infra.validation",
- "infra.scraping",
- "data.health",
- "data.onchain",
- "data.security",
- "infra.security",
- "compute.utility",
- "crypto.token-safety",
- "data.energy",
- "infra.creative",
- "compute.nlp",
- "data.reference",
- "commerce.general",
- "data.research",
- "data.utility",
- "infra.compliance",
- "verification",
- "data.x402",
- "infra.payments",
- "commerce.giftcards",
- "data.gaming",
- "data.validation",
- "infra.mcp",
- "ai.text",
- "compute.rendering"
-]New value: +[
+ "data.misc",
+ "data.crypto",
+ "data.stocks",
+ "data.search",
+ "data.defi",
+ "data.intelligence",
+ "infra.utility",
+ "data.macro",
+ "data.fx",
+ "infra.inference",
+ "data.enrichment",
+ "data.derivatives",
+ "data.social",
+ "data.weather",
+ "infra.trust",
+ "infra.validation",
+ "infra.scraping",
+ "data.health",
+ "data.onchain",
+ "data.security",
+ "infra.security",
+ "compute.utility",
+ "crypto.token-safety",
+ "data.energy",
+ "infra.creative",
+ "compute.nlp",
+ "data.reference",
+ "commerce.general",
+ "data.research",
+ "data.utility",
+ "infra.compliance",
+ "verification",
+ "data.validation",
+ "data.x402",
+ "infra.payments",
+ "commerce.giftcards",
+ "data.gaming",
+ "infra.mcp",
+ "ai.text",
+ "compute.rendering"
+]find_paid_service1 field changedInput schema / properties / category / enumPrevious value: -[
- "data.misc",
- "data.crypto",
- "data.stocks",
- "data.search",
- "data.defi",
- "data.intelligence",
- "infra.utility",
- "data.macro",
- "data.fx",
- "data.enrichment",
- "infra.inference",
- "data.derivatives",
- "data.social",
- "data.weather",
- "infra.trust",
- "infra.validation",
- "infra.scraping",
- "data.health",
- "data.onchain",
- "data.security",
- "infra.security",
- "compute.utility",
- "crypto.token-safety",
- "data.energy",
- "infra.creative",
- "compute.nlp",
- "data.reference",
- "commerce.general",
- "data.research",
- "data.utility",
- "infra.compliance",
- "verification",
- "data.x402",
- "infra.payments",
- "commerce.giftcards",
- "data.gaming",
- "data.validation",
- "infra.mcp",
- "ai.text",
- "compute.rendering"
-]New value: +[
+ "data.misc",
+ "data.crypto",
+ "data.stocks",
+ "data.search",
+ "data.defi",
+ "data.intelligence",
+ "infra.utility",
+ "data.macro",
+ "data.fx",
+ "infra.inference",
+ "data.enrichment",
+ "data.derivatives",
+ "data.social",
+ "data.weather",
+ "infra.trust",
+ "infra.validation",
+ "infra.scraping",
+ "data.health",
+ "data.onchain",
+ "data.security",
+ "infra.security",
+ "compute.utility",
+ "crypto.token-safety",
+ "data.energy",
+ "infra.creative",
+ "compute.nlp",
+ "data.reference",
+ "commerce.general",
+ "data.research",
+ "data.utility",
+ "infra.compliance",
+ "verification",
+ "data.x402",
+ "infra.payments",
+ "commerce.giftcards",
+ "data.gaming",
+ "data.validation",
+ "infra.mcp",
+ "ai.text",
+ "compute.rendering"
+]Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
Live x402 endpoint trust/diligence check before you pay it. $0.02/call via x402.
Inspect and validate an x402 endpoint before an autonomous agent spends USDC.
Measured x402 ecosystem data, facilitator reliability, and live endpoint checks.
Uptime and price-honesty oracle for x402: trust status, attestations, USDC history.
Add one secure layer between your agents and this server.
Each tool maps to a distinct stage: find_paid_service searches by need, get_service_details fetches details by listing id, and resolve_endpoint checks an arbitrary URL before spending. Although get_service_details and resolve_endpoint return similar records, their input types and intended use cases are clearly separated.
All three tool names follow a consistent verb_noun snake_case pattern: find_paid_service, get_service_details, and resolve_endpoint. The verbs clearly indicate their actions and the nouns identify their targets.
Three tools is compact but well-scoped for a directory and verification registry: discover, inspect, and verify. Each tool serves a distinct and necessary part of the pre-payment workflow, with no redundancy.
The tool surface covers the core user journey for the domain: finding a paid service, getting its full record, and checking an existing endpoint before paying. Since nohumans maintains and verifies listings itself, create/update/delete tools are not expected, and actual payment execution is outside the directory's purpose.