We buy from x402 endpoints with real USDC and publish delivery outcomes. Check before you spend.
Scored across 4 tools
Each tool serves a clearly distinct task: finding services by need, fetching details by listing ID, checking an already-held URL, and viewing aggregate demand. The descriptions even provide explicit 'use this when' guidance, making misselection unlikely.
Three tools follow a consistent verb_noun snake_case pattern (find_paid_service, get_service_details, resolve_endpoint). The fourth, what_agents_are_asking_for, is a question-style name rather than a verb command, which is a minor but noticeable deviation.
Four tools is proportionate for a specialized directory server. Each tool covers a distinct step in the user journey with no redundancy, and the set is well within the ideal 3-15 tool range.
The tool surface covers the full workflow for this domain: discover a service, inspect a specific listing, validate a URL before spending, and understand market demand as a potential seller. There are no obvious dead ends for the directory's stated purpose.
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 readOnly, openWorld, idempotent, and non-destructive hints. The description adds substantive context beyond those: how the registry is built (nohumans pays real USDC), the recency-weighted reputation scoring, the ranking order, the has_sample semantics ('you can cheaply test real output'), and the open-world meaning of zero results. No contradictions with annotations.
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 long but front-loaded with purpose and ranking, then moves to usage semantics. Nearly every sentence earns its place; the only minor redundancy is the query-quality advice, which is restated two or three times ('always describe the actual need', 'exact wording improves this directory', 'bare filter tells us far less'). Still efficient for a tool with this much marketplace nuance.
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?
For a complex paid-marketplace search tool, this description covers the registry's verification model, ranking order, sample-testing semantics, zero-results handling, and query best practices. An output schema exists to carry return values, annotations carry the safety profile, and the description fills the remaining behavioral and usage gaps. Nothing an agent needs to call it correctly 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 coverage is 100%, so baseline is 3. The description meaningfully extends the schema: it elevates `query` to the primary signal ('the only place that level of detail is captured'), clarifies that `category` is a coarse filter with text-search fallback for unmatched categories, and explains that max_price/min_score are conservative filters on top of free-text search. This adds real value beyond the input 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 states a specific verb (search), resource (registry of paid x402 APIs/datasets), and a differentiating mechanism (verified by real paid purchases). The ranking semantics and the mention of 'verified listings first' clearly distinguish this tool from siblings like get_service_details and resolve_endpoint without needing to open any schema.
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?
Explicitly says 'Use this before spending money to find services that actually work' and gives concrete selection guidance ('Prefer results with status verified and score >= 0.8'). It also tells the agent how to handle zero results (do not invent endpoints). It does not explicitly name sibling alternatives or exclusion conditions, but the context is strong.
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. A one-word paid verdict for the same listing — pay / caution / avoid with printed reasons, $0.005 USDC on Base via x402 — is at GET https://api.nohumans.directory/v1/listings/{id}/verdict; every fact behind it is in this record for free, so buy the verdict only when you want the rule applied for you.
| 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_sentinel | 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 | |
| paid_verification_latest | No | |
| onchain_unique_payers_30d | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly/idempotent/non-destructive, and the description adds real value beyond them: the record is free, it is led by an on-chain-verified paid_verification field, and it exposes reliability signals like consecutive failures. It stops short of describing pagination or error behavior, but for a read-only lookup this is a strong 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?
Front-loaded with purpose and the paid_verification lead, then usage guidance, then the alternative endpoint — a sensible ordering. The closing pitch ('every fact behind it is in this record for free...') is mildly promotional but still conveys a routing decision, so it mostly earns its place.
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?
For a single-id lookup with an output schema present, the definition covers what is needed: the input source, the shape of the returned record, why to call it before a paid request, and where the paid alternative lives. Nothing an agent needs to invoke it correctly 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?
Only one parameter and schema coverage is 100%, with the schema itself already saying the id comes from find_paid_service, so the description largely repeats the schema's provenance note. No additional format or syntax guidance is offered, making this a baseline 3.
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?
States a specific verb and resource ('fetch the full record for one listing by id') and enumerates the payload it leads with (paid_verification, settlement tx hash, schemas, chains, pricing, reputation). It explicitly anchors itself to find_paid_service results, so the agent can distinguish it from siblings without opening a schema.
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?
Gives an explicit when-to-use rule: '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 names an alternative paid endpoint and the condition that would select it ('buy the verdict only when you want the rule applied for you').
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. A one-word paid verdict for the same listing — pay / caution / avoid with printed reasons, $0.005 USDC on Base via x402 — is at GET https://api.nohumans.directory/v1/listings/{id}/verdict; every fact behind it is in this record for free, so buy the verdict only when you want the rule applied for you.
| 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?
Annotations already carry read-only, open-world, and idempotent hints, and the description adds meaningful context: the three possible match outcomes, the delisted-as-warning behavior, and the critical caveat that not-listed is not a safety verdict. This goes well beyond the structured annotations.
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 use-case routing, and the important not-listed caveat is clearly flagged. However, the tail about the paid verdict endpoint, pricing, and chain details is extra information not needed to call this tool correctly, so it loses a point.
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?
For a single-parameter read-only tool with an output schema, the description covers the key decision factors: when to call it, what the result categories mean, and how it relates to sibling tools. Nothing essential for correct invocation 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 documents the single url parameter fully, including query-string significance and tolerance for trailing slashes. The description provides usage context but does not add meaning about the parameter beyond what the schema covers, so baseline 3 is appropriate.
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 specific action and resource: a pre-spend verdict on an endpoint URL. It clearly distinguishes this tool from siblings by referencing get_service_details' record shape and find_paid_service's alternative role.
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?
Explicitly states when to use this tool ('when you have a URL in hand and no listing id') and names the alternative ('use find_paid_service instead when you have a need but no URL'). It also clarifies how to interpret a not-listed result, which is essential behavioral guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
What buyers actually searched this directory for, for an agent deciding which x402 service to build or list. Returns the aggregate demand feed: the terms asked most persistently (ranked by how many distinct days a term was asked, not by volume — volume is trivially faked and we proved it on ourselves), and the category filters they used. It reports what was ASKED, not what is missing: whether the listings already serving a term are adequate competition is a seller's judgement, not ours, and we grade those listings. Three exclusions are applied and published rather than hidden: queries under 5 characters (catalogue enumeration, once the top ten terms were the single letters a-j), searches from clients that also edit listings here (sellers checking their own rank — one accounted for 196 of 205 searches of the top term), and a floor of 3 distinct non-seller client IPs before any term appears at all. Client IPs are a ceiling on independent demand, never a count of buyers: one serverless caller presented eight IPs in a second. The window is complete but closed — it ends a day behind live, and the response says exactly when. This is a small market and the numbers are small; they are reported as they are so you can judge whether they are enough to act on.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
| Name | Required | Description |
|---|---|---|
| note | No | The exclusions, stated in words. |
| top_needs | Yes | Terms ranked by how many distinct days they were asked. |
| delay_hours | Yes | How far behind live the window ends. |
| window_days | Yes | Length of the reported window. |
| total_queries | Yes | Every search in the window, before exclusions. |
| window_ends_at | No | Unix seconds at which the window closes. |
| k_anonymity_unit | No | |
| k_anonymity_floor | No | Distinct non-seller client IPs a term needs before it is reported at all. |
| distinct_client_ips | No | A ceiling on independent demand, never a count of buyers. |
| top_category_filters | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only establish a safe read operation; the description goes far beyond by disclosing the ranking method (distinct days, not volume), three named exclusions with rationale, the closed window lagging one day behind live, and the IP-ceiling caveat for interpreting counts. This is exactly the interpretive context an agent needs and could not get from structured fields.
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?
Purpose is front-loaded in the first sentence and the remaining content is dense with caveats that materially affect interpretation. It is a single long paragraph with some editorial flourish ('we proved it on ourselves'), which costs a point, but nearly every clause carries substantive meaning.
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?
With an output schema present, return values need not be explained; the description instead supplies the methodology, exclusions, and window semantics required to read the numbers correctly, including a warning that the market is small. Nothing material is missing for correct use.
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 tool takes zero parameters, so the baseline is 4. The description nonetheless clarifies that category filters are returned as part of the feed, adding interpretive meaning without needing parameter documentation.
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 first sentence names a specific resource (the aggregate demand feed of what buyers searched this directory for) and a specific audience/decision (an agent deciding which x402 service to build or list). It is clearly distinct from the sibling tools, which are all about individual services rather than aggregate demand.
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?
It states the context of use clearly ('for an agent deciding which x402 service to build or list') and delineates a scope boundary ('reports what was ASKED, not what is missing'). It does not explicitly name alternatives or when-not-to-use conditions, but the target decision is unmistakable.
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.
find_paid_service1 field changedInput schema / properties / category / enumPrevious value: -[
- "data.other",
- "data.crypto",
- "data.misc",
- "data.web",
- "data.markets",
- "data.weather",
- "compute.llm",
- "compute.media",
- "data.geo",
- "data.fx",
- "data.stocks",
- "compute.tools",
- "data.search",
- "data.defi",
- "data.news",
- "data.intelligence",
- "infra.utility",
- "data.contacts",
- "data.macro",
- "data.enrichment",
- "data.derivatives",
- "infra.trust",
- "data.research",
- "data.social",
- "infra.inference",
- "infra.validation",
- "compute.nlp",
- "data.reference",
- "data.security",
- "infra.scraping",
- "data.energy",
- "data.onchain",
- "verification",
- "data.x402",
- "compute.utility",
- "data.health",
- "infra.security",
- "crypto.token-safety",
- "data.utility",
- "ai.agents"
-]New value: +[
+ "data.other",
+ "data.crypto",
+ "data.misc",
+ "data.web",
+ "data.markets",
+ "data.weather",
+ "compute.llm",
+ "compute.media",
+ "data.geo",
+ "data.fx",
+ "data.stocks",
+ "compute.tools",
+ "data.search",
+ "data.defi",
+ "data.news",
+ "data.intelligence",
+ "infra.utility",
+ "data.contacts",
+ "data.macro",
+ "data.enrichment",
+ "data.derivatives",
+ "infra.trust",
+ "data.research",
+ "data.social",
+ "infra.inference",
+ "infra.validation",
+ "compute.nlp",
+ "data.reference",
+ "data.security",
+ "infra.scraping",
+ "data.energy",
+ "data.onchain",
+ "data.x402",
+ "verification",
+ "compute.utility",
+ "data.health",
+ "infra.security",
+ "crypto.token-safety",
+ "data.utility",
+ "ai.agents"
+]find_paid_service1 field changedInput schema / properties / category / enumPrevious value: -[
- "data.other",
- "data.crypto",
- "data.misc",
- "data.web",
- "data.markets",
- "data.weather",
- "compute.llm",
- "compute.media",
- "data.geo",
- "data.fx",
- "data.stocks",
- "compute.tools",
- "data.search",
- "data.defi",
- "data.news",
- "data.intelligence",
- "infra.utility",
- "data.contacts",
- "data.macro",
- "data.enrichment",
- "data.derivatives",
- "infra.trust",
- "data.social",
- "infra.inference",
- "data.research",
- "infra.validation",
- "compute.nlp",
- "data.reference",
- "data.security",
- "infra.scraping",
- "data.energy",
- "data.onchain",
- "verification",
- "data.x402",
- "compute.utility",
- "data.health",
- "infra.security",
- "crypto.token-safety",
- "data.utility",
- "infra.creative"
-]New value: +[
+ "data.other",
+ "data.crypto",
+ "data.misc",
+ "data.web",
+ "data.markets",
+ "data.weather",
+ "compute.llm",
+ "compute.media",
+ "data.geo",
+ "data.fx",
+ "data.stocks",
+ "compute.tools",
+ "data.search",
+ "data.defi",
+ "data.news",
+ "data.intelligence",
+ "infra.utility",
+ "data.contacts",
+ "data.macro",
+ "data.enrichment",
+ "data.derivatives",
+ "infra.trust",
+ "data.research",
+ "data.social",
+ "infra.inference",
+ "infra.validation",
+ "compute.nlp",
+ "data.reference",
+ "data.security",
+ "infra.scraping",
+ "data.energy",
+ "data.onchain",
+ "verification",
+ "data.x402",
+ "compute.utility",
+ "data.health",
+ "infra.security",
+ "crypto.token-safety",
+ "data.utility",
+ "ai.agents"
+]find_paid_service1 field changedInput schema / properties / category / enumPrevious value: -[
- "data.other",
- "data.crypto",
- "data.misc",
- "data.web",
- "data.markets",
- "data.weather",
- "compute.llm",
- "compute.media",
- "data.geo",
- "data.fx",
- "data.stocks",
- "compute.tools",
- "data.search",
- "data.defi",
- "data.news",
- "data.intelligence",
- "infra.utility",
- "data.contacts",
- "data.macro",
- "data.enrichment",
- "data.derivatives",
- "infra.trust",
- "data.social",
- "infra.inference",
- "data.research",
- "infra.validation",
- "compute.nlp",
- "data.reference",
- "data.security",
- "infra.scraping",
- "data.energy",
- "data.onchain",
- "verification",
- "compute.utility",
- "data.health",
- "data.x402",
- "infra.security",
- "crypto.token-safety",
- "data.utility",
- "infra.creative"
-]New value: +[
+ "data.other",
+ "data.crypto",
+ "data.misc",
+ "data.web",
+ "data.markets",
+ "data.weather",
+ "compute.llm",
+ "compute.media",
+ "data.geo",
+ "data.fx",
+ "data.stocks",
+ "compute.tools",
+ "data.search",
+ "data.defi",
+ "data.news",
+ "data.intelligence",
+ "infra.utility",
+ "data.contacts",
+ "data.macro",
+ "data.enrichment",
+ "data.derivatives",
+ "infra.trust",
+ "data.social",
+ "infra.inference",
+ "data.research",
+ "infra.validation",
+ "compute.nlp",
+ "data.reference",
+ "data.security",
+ "infra.scraping",
+ "data.energy",
+ "data.onchain",
+ "verification",
+ "data.x402",
+ "compute.utility",
+ "data.health",
+ "infra.security",
+ "crypto.token-safety",
+ "data.utility",
+ "infra.creative"
+]find_paid_service1 field changedInput schema / properties / category / enumPrevious value: -[
- "data.other",
- "data.crypto",
- "data.misc",
- "data.web",
- "data.markets",
- "data.weather",
- "compute.llm",
- "compute.media",
- "data.geo",
- "data.fx",
- "data.stocks",
- "compute.tools",
- "data.search",
- "data.defi",
- "data.intelligence",
- "data.news",
- "infra.utility",
- "data.contacts",
- "data.macro",
- "data.enrichment",
- "data.derivatives",
- "infra.trust",
- "data.social",
- "infra.inference",
- "data.research",
- "infra.validation",
- "compute.nlp",
- "data.reference",
- "data.security",
- "infra.scraping",
- "data.energy",
- "data.onchain",
- "verification",
- "compute.utility",
- "data.health",
- "data.x402",
- "infra.security",
- "crypto.token-safety",
- "data.utility",
- "infra.creative"
-]New value: +[
+ "data.other",
+ "data.crypto",
+ "data.misc",
+ "data.web",
+ "data.markets",
+ "data.weather",
+ "compute.llm",
+ "compute.media",
+ "data.geo",
+ "data.fx",
+ "data.stocks",
+ "compute.tools",
+ "data.search",
+ "data.defi",
+ "data.news",
+ "data.intelligence",
+ "infra.utility",
+ "data.contacts",
+ "data.macro",
+ "data.enrichment",
+ "data.derivatives",
+ "infra.trust",
+ "data.social",
+ "infra.inference",
+ "data.research",
+ "infra.validation",
+ "compute.nlp",
+ "data.reference",
+ "data.security",
+ "infra.scraping",
+ "data.energy",
+ "data.onchain",
+ "verification",
+ "compute.utility",
+ "data.health",
+ "data.x402",
+ "infra.security",
+ "crypto.token-safety",
+ "data.utility",
+ "infra.creative"
+]find_paid_service1 field changedInput schema / properties / category / enumPrevious value: -[
- "data.other",
- "data.crypto",
- "data.misc",
- "data.web",
- "data.markets",
- "data.weather",
- "compute.llm",
- "compute.media",
- "data.geo",
- "data.fx",
- "data.stocks",
- "compute.tools",
- "data.search",
- "data.defi",
- "data.intelligence",
- "data.news",
- "data.contacts",
- "infra.utility",
- "data.macro",
- "data.enrichment",
- "data.derivatives",
- "infra.trust",
- "data.social",
- "infra.inference",
- "data.research",
- "infra.validation",
- "compute.nlp",
- "data.reference",
- "data.security",
- "infra.scraping",
- "data.energy",
- "data.onchain",
- "verification",
- "compute.utility",
- "data.health",
- "data.x402",
- "infra.security",
- "crypto.token-safety",
- "data.utility",
- "infra.creative"
-]New value: +[
+ "data.other",
+ "data.crypto",
+ "data.misc",
+ "data.web",
+ "data.markets",
+ "data.weather",
+ "compute.llm",
+ "compute.media",
+ "data.geo",
+ "data.fx",
+ "data.stocks",
+ "compute.tools",
+ "data.search",
+ "data.defi",
+ "data.intelligence",
+ "data.news",
+ "infra.utility",
+ "data.contacts",
+ "data.macro",
+ "data.enrichment",
+ "data.derivatives",
+ "infra.trust",
+ "data.social",
+ "infra.inference",
+ "data.research",
+ "infra.validation",
+ "compute.nlp",
+ "data.reference",
+ "data.security",
+ "infra.scraping",
+ "data.energy",
+ "data.onchain",
+ "verification",
+ "compute.utility",
+ "data.health",
+ "data.x402",
+ "infra.security",
+ "crypto.token-safety",
+ "data.utility",
+ "infra.creative"
+]find_paid_service1 field changedInput schema / properties / category / enumPrevious value: -[
- "data.other",
- "data.crypto",
- "data.misc",
- "data.web",
- "data.markets",
- "data.weather",
- "compute.llm",
- "compute.media",
- "data.geo",
- "data.fx",
- "data.stocks",
- "compute.tools",
- "data.search",
- "data.defi",
- "data.intelligence",
- "data.news",
- "data.contacts",
- "infra.utility",
- "data.macro",
- "data.enrichment",
- "data.derivatives",
- "infra.trust",
- "data.social",
- "infra.inference",
- "data.research",
- "infra.validation",
- "compute.nlp",
- "data.reference",
- "data.security",
- "infra.scraping",
- "data.energy",
- "data.onchain",
- "verification",
- "compute.utility",
- "data.health",
- "infra.security",
- "data.x402",
- "crypto.token-safety",
- "data.utility",
- "infra.creative"
-]New value: +[
+ "data.other",
+ "data.crypto",
+ "data.misc",
+ "data.web",
+ "data.markets",
+ "data.weather",
+ "compute.llm",
+ "compute.media",
+ "data.geo",
+ "data.fx",
+ "data.stocks",
+ "compute.tools",
+ "data.search",
+ "data.defi",
+ "data.intelligence",
+ "data.news",
+ "data.contacts",
+ "infra.utility",
+ "data.macro",
+ "data.enrichment",
+ "data.derivatives",
+ "infra.trust",
+ "data.social",
+ "infra.inference",
+ "data.research",
+ "infra.validation",
+ "compute.nlp",
+ "data.reference",
+ "data.security",
+ "infra.scraping",
+ "data.energy",
+ "data.onchain",
+ "verification",
+ "compute.utility",
+ "data.health",
+ "data.x402",
+ "infra.security",
+ "crypto.token-safety",
+ "data.utility",
+ "infra.creative"
+]find_paid_service1 field changedInput schema / properties / category / enumPrevious value: -[
- "data.other",
- "data.crypto",
- "data.misc",
- "data.web",
- "data.markets",
- "data.weather",
- "compute.llm",
- "compute.media",
- "data.geo",
- "data.fx",
- "data.stocks",
- "compute.tools",
- "data.search",
- "data.defi",
- "data.intelligence",
- "data.news",
- "data.contacts",
- "infra.utility",
- "data.macro",
- "data.enrichment",
- "data.derivatives",
- "data.social",
- "infra.inference",
- "infra.trust",
- "data.research",
- "infra.validation",
- "compute.nlp",
- "data.reference",
- "data.security",
- "infra.scraping",
- "data.energy",
- "data.onchain",
- "verification",
- "compute.utility",
- "data.health",
- "infra.security",
- "data.x402",
- "crypto.token-safety",
- "data.utility",
- "infra.creative"
-]New value: +[
+ "data.other",
+ "data.crypto",
+ "data.misc",
+ "data.web",
+ "data.markets",
+ "data.weather",
+ "compute.llm",
+ "compute.media",
+ "data.geo",
+ "data.fx",
+ "data.stocks",
+ "compute.tools",
+ "data.search",
+ "data.defi",
+ "data.intelligence",
+ "data.news",
+ "data.contacts",
+ "infra.utility",
+ "data.macro",
+ "data.enrichment",
+ "data.derivatives",
+ "infra.trust",
+ "data.social",
+ "infra.inference",
+ "data.research",
+ "infra.validation",
+ "compute.nlp",
+ "data.reference",
+ "data.security",
+ "infra.scraping",
+ "data.energy",
+ "data.onchain",
+ "verification",
+ "compute.utility",
+ "data.health",
+ "infra.security",
+ "data.x402",
+ "crypto.token-safety",
+ "data.utility",
+ "infra.creative"
+]find_paid_service1 field changedInput schema / properties / category / enumPrevious value: -[
- "data.other",
- "data.crypto",
- "data.misc",
- "data.web",
- "data.markets",
- "data.weather",
- "compute.llm",
- "compute.media",
- "data.geo",
- "data.fx",
- "data.stocks",
- "compute.tools",
- "data.search",
- "data.defi",
- "data.intelligence",
- "data.news",
- "data.contacts",
- "infra.utility",
- "data.macro",
- "data.enrichment",
- "data.derivatives",
- "data.social",
- "infra.inference",
- "infra.trust",
- "infra.validation",
- "data.research",
- "compute.nlp",
- "data.reference",
- "data.security",
- "infra.scraping",
- "data.energy",
- "data.onchain",
- "verification",
- "compute.utility",
- "data.health",
- "infra.security",
- "data.x402",
- "crypto.token-safety",
- "data.utility",
- "infra.creative"
-]New value: +[
+ "data.other",
+ "data.crypto",
+ "data.misc",
+ "data.web",
+ "data.markets",
+ "data.weather",
+ "compute.llm",
+ "compute.media",
+ "data.geo",
+ "data.fx",
+ "data.stocks",
+ "compute.tools",
+ "data.search",
+ "data.defi",
+ "data.intelligence",
+ "data.news",
+ "data.contacts",
+ "infra.utility",
+ "data.macro",
+ "data.enrichment",
+ "data.derivatives",
+ "data.social",
+ "infra.inference",
+ "infra.trust",
+ "data.research",
+ "infra.validation",
+ "compute.nlp",
+ "data.reference",
+ "data.security",
+ "infra.scraping",
+ "data.energy",
+ "data.onchain",
+ "verification",
+ "compute.utility",
+ "data.health",
+ "infra.security",
+ "data.x402",
+ "crypto.token-safety",
+ "data.utility",
+ "infra.creative"
+]find_paid_service1 field changedInput schema / properties / category / enumPrevious value: -[
- "data.other",
- "data.crypto",
- "data.misc",
- "data.web",
- "data.markets",
- "data.weather",
- "compute.llm",
- "compute.media",
- "data.geo",
- "data.fx",
- "data.stocks",
- "compute.tools",
- "data.search",
- "data.defi",
- "data.intelligence",
- "data.news",
- "data.contacts",
- "infra.utility",
- "data.macro",
- "data.enrichment",
- "data.derivatives",
- "infra.inference",
- "data.social",
- "infra.trust",
- "infra.validation",
- "data.research",
- "compute.nlp",
- "data.reference",
- "data.security",
- "infra.scraping",
- "data.energy",
- "data.onchain",
- "verification",
- "compute.utility",
- "data.health",
- "infra.security",
- "data.x402",
- "crypto.token-safety",
- "data.utility",
- "infra.creative"
-]New value: +[
+ "data.other",
+ "data.crypto",
+ "data.misc",
+ "data.web",
+ "data.markets",
+ "data.weather",
+ "compute.llm",
+ "compute.media",
+ "data.geo",
+ "data.fx",
+ "data.stocks",
+ "compute.tools",
+ "data.search",
+ "data.defi",
+ "data.intelligence",
+ "data.news",
+ "data.contacts",
+ "infra.utility",
+ "data.macro",
+ "data.enrichment",
+ "data.derivatives",
+ "data.social",
+ "infra.inference",
+ "infra.trust",
+ "infra.validation",
+ "data.research",
+ "compute.nlp",
+ "data.reference",
+ "data.security",
+ "infra.scraping",
+ "data.energy",
+ "data.onchain",
+ "verification",
+ "compute.utility",
+ "data.health",
+ "infra.security",
+ "data.x402",
+ "crypto.token-safety",
+ "data.utility",
+ "infra.creative"
+]find_paid_service1 field changedInput schema / properties / category / enumPrevious value: -[
- "data.other",
- "data.crypto",
- "data.misc",
- "data.web",
- "data.markets",
- "data.weather",
- "compute.llm",
- "compute.media",
- "data.geo",
- "data.fx",
- "data.stocks",
- "compute.tools",
- "data.search",
- "data.defi",
- "data.intelligence",
- "data.news",
- "infra.utility",
- "data.contacts",
- "data.macro",
- "data.enrichment",
- "data.derivatives",
- "data.social",
- "infra.inference",
- "infra.trust",
- "infra.validation",
- "data.research",
- "compute.nlp",
- "data.reference",
- "data.security",
- "infra.scraping",
- "data.energy",
- "data.onchain",
- "verification",
- "compute.utility",
- "data.health",
- "infra.security",
- "data.x402",
- "crypto.token-safety",
- "data.utility",
- "infra.creative"
-]New value: +[
+ "data.other",
+ "data.crypto",
+ "data.misc",
+ "data.web",
+ "data.markets",
+ "data.weather",
+ "compute.llm",
+ "compute.media",
+ "data.geo",
+ "data.fx",
+ "data.stocks",
+ "compute.tools",
+ "data.search",
+ "data.defi",
+ "data.intelligence",
+ "data.news",
+ "data.contacts",
+ "infra.utility",
+ "data.macro",
+ "data.enrichment",
+ "data.derivatives",
+ "infra.inference",
+ "data.social",
+ "infra.trust",
+ "infra.validation",
+ "data.research",
+ "compute.nlp",
+ "data.reference",
+ "data.security",
+ "infra.scraping",
+ "data.energy",
+ "data.onchain",
+ "verification",
+ "compute.utility",
+ "data.health",
+ "infra.security",
+ "data.x402",
+ "crypto.token-safety",
+ "data.utility",
+ "infra.creative"
+]find_paid_service1 field changedInput schema / properties / category / enumPrevious value: -[
- "data.other",
- "data.crypto",
- "data.misc",
- "data.web",
- "data.markets",
- "data.weather",
- "compute.llm",
- "compute.media",
- "data.geo",
- "data.fx",
- "data.stocks",
- "compute.tools",
- "data.search",
- "data.defi",
- "data.intelligence",
- "data.news",
- "infra.utility",
- "data.contacts",
- "data.macro",
- "data.enrichment",
- "data.derivatives",
- "data.social",
- "infra.trust",
- "infra.inference",
- "infra.validation",
- "data.research",
- "compute.nlp",
- "data.reference",
- "data.security",
- "infra.scraping",
- "data.energy",
- "data.onchain",
- "verification",
- "compute.utility",
- "data.health",
- "infra.security",
- "data.x402",
- "crypto.token-safety",
- "data.utility",
- "infra.creative"
-]New value: +[
+ "data.other",
+ "data.crypto",
+ "data.misc",
+ "data.web",
+ "data.markets",
+ "data.weather",
+ "compute.llm",
+ "compute.media",
+ "data.geo",
+ "data.fx",
+ "data.stocks",
+ "compute.tools",
+ "data.search",
+ "data.defi",
+ "data.intelligence",
+ "data.news",
+ "infra.utility",
+ "data.contacts",
+ "data.macro",
+ "data.enrichment",
+ "data.derivatives",
+ "data.social",
+ "infra.inference",
+ "infra.trust",
+ "infra.validation",
+ "data.research",
+ "compute.nlp",
+ "data.reference",
+ "data.security",
+ "infra.scraping",
+ "data.energy",
+ "data.onchain",
+ "verification",
+ "compute.utility",
+ "data.health",
+ "infra.security",
+ "data.x402",
+ "crypto.token-safety",
+ "data.utility",
+ "infra.creative"
+]find_paid_service1 field changedInput schema / properties / category / enumPrevious value: -[
- "data.other",
- "data.crypto",
- "data.misc",
- "data.web",
- "data.markets",
- "data.weather",
- "compute.llm",
- "compute.media",
- "data.geo",
- "data.fx",
- "data.stocks",
- "compute.tools",
- "data.search",
- "data.defi",
- "data.intelligence",
- "data.news",
- "infra.utility",
- "data.contacts",
- "data.macro",
- "data.enrichment",
- "data.derivatives",
- "data.social",
- "infra.inference",
- "infra.trust",
- "infra.validation",
- "data.research",
- "compute.nlp",
- "data.reference",
- "data.security",
- "infra.scraping",
- "data.energy",
- "data.onchain",
- "verification",
- "compute.utility",
- "data.health",
- "infra.security",
- "data.x402",
- "crypto.token-safety",
- "data.utility",
- "infra.creative"
-]New value: +[
+ "data.other",
+ "data.crypto",
+ "data.misc",
+ "data.web",
+ "data.markets",
+ "data.weather",
+ "compute.llm",
+ "compute.media",
+ "data.geo",
+ "data.fx",
+ "data.stocks",
+ "compute.tools",
+ "data.search",
+ "data.defi",
+ "data.intelligence",
+ "data.news",
+ "infra.utility",
+ "data.contacts",
+ "data.macro",
+ "data.enrichment",
+ "data.derivatives",
+ "data.social",
+ "infra.trust",
+ "infra.inference",
+ "infra.validation",
+ "data.research",
+ "compute.nlp",
+ "data.reference",
+ "data.security",
+ "infra.scraping",
+ "data.energy",
+ "data.onchain",
+ "verification",
+ "compute.utility",
+ "data.health",
+ "infra.security",
+ "data.x402",
+ "crypto.token-safety",
+ "data.utility",
+ "infra.creative"
+]find_paid_service1 field changedInput schema / properties / category / enumPrevious 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.contacts",
- "data.macro",
- "data.enrichment",
- "data.derivatives",
- "data.social",
- "infra.inference",
- "infra.trust",
- "infra.validation",
- "data.research",
- "compute.nlp",
- "data.reference",
- "data.security",
- "infra.scraping",
- "data.energy",
- "data.onchain",
- "verification",
- "compute.utility",
- "data.health",
- "infra.security",
- "data.x402",
- "crypto.token-safety",
- "data.utility",
- "infra.creative"
-]New value: +[
+ "data.other",
+ "data.crypto",
+ "data.misc",
+ "data.web",
+ "data.markets",
+ "data.weather",
+ "compute.llm",
+ "compute.media",
+ "data.geo",
+ "data.fx",
+ "data.stocks",
+ "compute.tools",
+ "data.search",
+ "data.defi",
+ "data.intelligence",
+ "data.news",
+ "infra.utility",
+ "data.contacts",
+ "data.macro",
+ "data.enrichment",
+ "data.derivatives",
+ "data.social",
+ "infra.inference",
+ "infra.trust",
+ "infra.validation",
+ "data.research",
+ "compute.nlp",
+ "data.reference",
+ "data.security",
+ "infra.scraping",
+ "data.energy",
+ "data.onchain",
+ "verification",
+ "compute.utility",
+ "data.health",
+ "infra.security",
+ "data.x402",
+ "crypto.token-safety",
+ "data.utility",
+ "infra.creative"
+]find_paid_service1 field changedInput schema / properties / category / enumPrevious 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.contacts",
- "data.macro",
- "data.enrichment",
- "infra.inference",
- "data.social",
- "data.derivatives",
- "infra.trust",
- "infra.validation",
- "data.research",
- "compute.nlp",
- "data.reference",
- "data.security",
- "infra.scraping",
- "data.energy",
- "data.onchain",
- "verification",
- "compute.utility",
- "infra.security",
- "data.health",
- "infra.creative",
- "data.x402",
- "crypto.token-safety",
- "data.utility"
-]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.contacts",
+ "data.macro",
+ "data.enrichment",
+ "data.derivatives",
+ "data.social",
+ "infra.inference",
+ "infra.trust",
+ "infra.validation",
+ "data.research",
+ "compute.nlp",
+ "data.reference",
+ "data.security",
+ "infra.scraping",
+ "data.energy",
+ "data.onchain",
+ "verification",
+ "compute.utility",
+ "data.health",
+ "infra.security",
+ "data.x402",
+ "crypto.token-safety",
+ "data.utility",
+ "infra.creative"
+]find_paid_service1 field changedInput schema / properties / category / enumPrevious 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.contacts",
- "data.macro",
- "data.enrichment",
- "infra.inference",
- "data.social",
- "data.derivatives",
- "infra.trust",
- "infra.validation",
- "data.research",
- "compute.nlp",
- "data.reference",
- "data.security",
- "infra.scraping",
- "data.energy",
- "data.onchain",
- "verification",
- "compute.utility",
- "infra.security",
- "data.health",
- "infra.creative",
- "crypto.token-safety",
- "data.utility",
- "commerce.general"
-]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.contacts",
+ "data.macro",
+ "data.enrichment",
+ "infra.inference",
+ "data.social",
+ "data.derivatives",
+ "infra.trust",
+ "infra.validation",
+ "data.research",
+ "compute.nlp",
+ "data.reference",
+ "data.security",
+ "infra.scraping",
+ "data.energy",
+ "data.onchain",
+ "verification",
+ "compute.utility",
+ "infra.security",
+ "data.health",
+ "infra.creative",
+ "data.x402",
+ "crypto.token-safety",
+ "data.utility"
+]find_paid_service1 field changedInput schema / properties / category / enumPrevious 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.social",
- "data.derivatives",
- "infra.trust",
- "infra.validation",
- "data.research",
- "compute.nlp",
- "data.reference",
- "data.security",
- "infra.scraping",
- "data.energy",
- "data.onchain",
- "verification",
- "compute.utility",
- "infra.security",
- "data.health",
- "infra.creative",
- "crypto.token-safety",
- "data.utility",
- "commerce.general"
-]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.contacts",
+ "data.macro",
+ "data.enrichment",
+ "infra.inference",
+ "data.social",
+ "data.derivatives",
+ "infra.trust",
+ "infra.validation",
+ "data.research",
+ "compute.nlp",
+ "data.reference",
+ "data.security",
+ "infra.scraping",
+ "data.energy",
+ "data.onchain",
+ "verification",
+ "compute.utility",
+ "infra.security",
+ "data.health",
+ "infra.creative",
+ "crypto.token-safety",
+ "data.utility",
+ "commerce.general"
+]find_paid_service2 fields changedInput schema / properties / category / descriptionPrevious value: -"Category filter. Call get_categories-equivalent via GET /v1/categories for the live list, or omit and rely on free-text `query` instead — an unmatched category now falls back to text search rather than returning zero results."New value: +"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."Input schema / properties / category / enumAdded 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.social",
+ "data.derivatives",
+ "infra.trust",
+ "infra.validation",
+ "data.research",
+ "compute.nlp",
+ "data.reference",
+ "data.security",
+ "infra.scraping",
+ "data.energy",
+ "data.onchain",
+ "verification",
+ "compute.utility",
+ "infra.security",
+ "data.health",
+ "infra.creative",
+ "crypto.token-safety",
+ "data.utility",
+ "commerce.general"
+]find_paid_service2 fields changedInput schema / properties / category / descriptionPrevious value: -"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."New value: +"Category filter. Call get_categories-equivalent via GET /v1/categories for the live list, or omit and rely on free-text `query` instead — an unmatched category now falls back to text search rather than returning zero results."Input schema / properties / category / enumRemoved 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.social",
- "data.derivatives",
- "infra.trust",
- "infra.validation",
- "data.research",
- "compute.nlp",
- "data.reference",
- "data.security",
- "infra.scraping",
- "data.energy",
- "data.onchain",
- "verification",
- "compute.utility",
- "infra.security",
- "data.health",
- "infra.creative",
- "crypto.token-safety",
- "data.utility",
- "commerce.general"
-]find_paid_service1 field changedInput schema / properties / category / enumPrevious 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.intelligence",
- "data.defi",
- "data.news",
- "infra.utility",
- "data.macro",
- "data.contacts",
- "data.enrichment",
- "infra.inference",
- "data.social",
- "data.derivatives",
- "infra.trust",
- "infra.validation",
- "data.research",
- "compute.nlp",
- "data.reference",
- "data.security",
- "infra.scraping",
- "data.energy",
- "data.onchain",
- "verification",
- "compute.utility",
- "infra.security",
- "data.health",
- "infra.creative",
- "crypto.token-safety",
- "data.utility",
- "commerce.general"
-]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.social",
+ "data.derivatives",
+ "infra.trust",
+ "infra.validation",
+ "data.research",
+ "compute.nlp",
+ "data.reference",
+ "data.security",
+ "infra.scraping",
+ "data.energy",
+ "data.onchain",
+ "verification",
+ "compute.utility",
+ "infra.security",
+ "data.health",
+ "infra.creative",
+ "crypto.token-safety",
+ "data.utility",
+ "commerce.general"
+]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.