nohumans.directory

Get a paid service's full record

get_service_details

Read-onlyIdempotent

Full record for one listing id: request and response schemas, sample_query, observed 402 terms (network, payTo, scheme, x402 version), reputation detail, and paid_verification (our latest real USDC purchase, with its settlement tx where proven). Useful before paying: it shows the exact request shape and current reliability. Every timestamp has an _iso twin; on-chain counts describe the seller's wallet, usually shared by several listings, not this endpoint. Free, read-only.

Input Schema

Name	Required	Description	Default
`id`	Yes	Listing id: the id field of a search result, e.g. f094faea-d9d.

Output Schema

Name	Required	Description	Default
`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
`mpp_methods`	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_scope`	No
`onchain_shape`	No
`paid_verified`	No
`probes_failed`	No
`probes_passed`	No
`response_mime`	No
`last_probed_at`	No
`onchain_wallet`	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_verified_at`	No
`paid_verification`	No
`payment_protocols`	No
`status_changed_at`	No
`verdict_age_seconds`	No
`paid_verified_at_iso`	No
`payto_distinct_recent`	No
`paid_verification_latest`	No
`onchain_unique_payers_30d`	No
`onchain_payto_shared_listings`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 13, 2026

changedInput schema / properties / id / description

Previous value: -"Listing id, as returned by find_paid_service."New value: +"Listing id: the id field of a search result, e.g. f094faea-d9d."

Changed8 schema fields changedOct 10, 2026

removedOutput schema / properties / chains / description

Removed value: -"Networks you can PAY on, as declared by the seller. Not the data or chains the service covers."

removedOutput schema / properties / mpp_methods / description

Removed value: -"MPP methods as the endpoint names them (tempo, evm, stripe, ...); null when its 402 offers no MPP."

removedOutput schema / properties / onchain_payto_shared_listings / description

Removed value: -"Active listings naming the same payTo address. Above 1, the on-chain figures are the wallet's, not this endpoint's."

removedOutput schema / properties / onchain_scope / description

Removed value: -"What the on-chain figures describe, in words. Read before quoting them."

removedOutput schema / properties / onchain_wallet / description

Removed value: -"On-chain activity of the seller's payment wallet (payTo), usually shared by many listings: scope, shared_by_listings, pay_to, tx_count_30d, unique_payers_30d, volume_usd_30d. Not this endpoint's own usage."

removedOutput schema / properties / p50_latency_ms / description

Removed value: -"Median latency over the last 7 days (timeouts included); null under 5 probes."

removedOutput schema / properties / payment_protocols / description

Removed value: -"Protocols the endpoint's own 402 offered on our unpaid probes: x402, mpp, or both. Paid verification covers x402 on Base only."

removedOutput schema / properties / probe_count / description

Removed value: -"Every counted probe, passes AND failures. Passes are probes_passed."

Changed2 schema fields changedSep 26, 2026

addedOutput schema / properties / mpp_methods

Added value: +{
+  "description": "MPP methods as the endpoint names them (tempo, evm, stripe, ...); null when its 402 offers no MPP.",
+  "items": {
+    "type": "string"
+  },
+  "type": [
+    "array",
+    "null"
+  ]
+}

addedOutput schema / properties / payment_protocols

Added value: +{
+  "description": "Protocols the endpoint's own 402 offered on our unpaid probes: x402, mpp, or both. Paid verification covers x402 on Base only.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed2 schema fields changedSep 24, 2026

addedOutput schema / properties / onchain_wallet

Added value: +{
+  "additionalProperties": true,
+  "description": "On-chain activity of the seller's payment wallet (payTo), usually shared by many listings: scope, shared_by_listings, pay_to, tx_count_30d, unique_payers_30d, volume_usd_30d. Not this endpoint's own usage.",
+  "type": "object"
+}

addedOutput schema / properties / p50_latency_ms / description

Added value: +"Median latency over the last 7 days (timeouts included); null under 5 probes."

Changed8 schema fields changedSep 24, 2026

addedOutput schema / properties / chains / description

Added value: +"Networks you can PAY on, as declared by the seller. Not the data or chains the service covers."

addedOutput schema / properties / onchain_payto_shared_listings

Added value: +{
+  "description": "Active listings naming the same payTo address. Above 1, the on-chain figures are the wallet's, not this endpoint's.",
+  "type": [
+    "integer",
+    "null"
+  ]
+}

addedOutput schema / properties / onchain_scope

Added value: +{
+  "description": "What the on-chain figures describe, in words. Read before quoting them.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / paid_verified_at

Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}

addedOutput schema / properties / paid_verified_at_iso

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / probe_count / description

Added value: +"Every counted probe, passes AND failures. Passes are probes_passed."

addedOutput schema / properties / probes_failed

Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}

addedOutput schema / properties / probes_passed

Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}

Changed1 schema field changedSep 11, 2026
- addedOutput schema / properties / paid_verification_latest
```
Added value: +{
+  "type": [
+    "object",
+    "null"
+  ]
+}
```
Changed1 schema field changedSep 11, 2026
- addedOutput schema / properties / payto_sentinel
```
Added value: +{
+  "type": "boolean"
+}
```

Changed29 schema fields changedSep 1, 2026

addedOutput schema / properties / category
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / chains

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / description
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / distinct_payers

Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}

addedOutput schema / properties / endpoint_url
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / evidence_note

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / evidence_tier
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / has_sample
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / id
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / kind

Added value: +{
+  "enum": [
+    "api",
+    "agent"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / last_probed_at

Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}

addedOutput schema / properties / name
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / observed_network

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / onchain_unique_payers_30d

Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}

addedOutput schema / properties / p50_latency_ms

Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}

addedOutput schema / properties / p95_latency_ms

Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}

addedOutput schema / properties / p99_latency_ms

Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}

addedOutput schema / properties / paid_verified
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / price_amount
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / price_currency
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / probe_count

Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}

addedOutput schema / properties / report_count

Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}

addedOutput schema / properties / report_score

Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}

addedOutput schema / properties / response_mime

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / score

Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}

addedOutput schema / properties / status

Added value: +{
+  "enum": [
+    "verified",
+    "unverified",
+    "failing"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / status_changed_at

Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}

addedOutput schema / properties / verdict_age_seconds

Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}

addedOutput schema / properties / x402_version

Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}

Changed1 schema field changedSep 1, 2026

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"
+}

First observedJul 19, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds genuine context: observed 402 terms, the _iso timestamp twins, and the warning that on-chain counts describe the seller's shared wallet rather than this endpoint. That last caveat is exactly the kind of trap-preventing detail annotations cannot convey.

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

Conciseness4/5

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

One dense paragraph, front-loaded with the scope ('Full record for one listing id') before the payload inventory. Every sentence carries information, though the enumeration of fields is long enough to border on list-dumping.

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

Completeness4/5

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

An output schema exists, so return values need not be explained, and the description nonetheless flags the shared-wallet caveat and the _iso timestamps an agent could otherwise misread. Complete for a one-parameter read tool, with no unused gaps.

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

Parameters3/5

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

Schema coverage is 100% and the single id parameter is fully documented in the schema, so baseline is 3. The description only reinforces that the id is a listing id sourced from a search result — helpful, but nothing the schema does not already say.

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

Purpose4/5

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

States a specific verb and resource ('Full record for one listing id') and enumerates the payload contents (request/response schemas, sample_query, 402 terms, reputation, paid_verification), which clearly separates it from find_paid_service and resolve_endpoint. It never names a sibling explicitly, so it stops short of a 5.

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

Usage Guidelines4/5

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

'Useful before paying: it shows the exact request shape and current reliability' gives a concrete decision context for when to reach for this tool. It does not state when not to use it or point at the sibling that would replace it, so it is clear context without exclusions.

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

All nohumans.directory tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.