Agent and Developer Guidance
Naturepedia™ Discovery FAQ
Answers to the primary discovery, pricing, resource-selection, settlement, licensing, availability, validation, and interpretation questions for machine consumers.
What is the Naturepedia™ Discovery Index?
It is the authoritative human-readable directory for Naturepedia™ machine discovery, MCP access, AI guidance, canonical registries, pricing metadata, governance, provenance, resource availability, and protected x402 retrieval pathways.
Are the Naturepedia™ MCP tools paid?
No. MCP discovery and canonical resolution remain public and read-only. Separate protected HTTP resources may require class-specific x402 payments after the intended resource has been resolved, confirmed as registered and available, and returned a valid production HTTP 402 Payment Required challenge.
Which pricing classes are currently active?
Free discovery is active. The $0.005 Atomic canonical-query class and $0.025 Enriched relationship-query class are active for explicitly registered deterministic payloads. The $0.25 Structured Plate™ class is active for registered and validated Plate payloads. The $5.00 bounded subtree, Registry, or System Map class and the $25.00 full-Registry or Knowledge Mesh snapshot class are also active. Active class status does not mean every possible resource slug is payable; availability is determined at the resource level.
Which Atomic Query route is currently active?
The current verified Atomic Query route is /v1/query/atomic/robbie-george-biography-plate. It provides a narrowly bounded canonical identifier-resolution resource at 5,000 atomic units ($0.005 USDC). Its canonical internal route is /x402/query/atomic/robbie-george-biography-plate. The production HTTP 402 challenge has been verified at gateway tier atomic.
Which Enriched Query route is currently active?
The current verified Enriched Query route is /v1/query/enriched/robbie-george-biography-plate. It provides a bounded relationship-aware canonical response at 25,000 atomic units ($0.025 USDC). Its production HTTP 402 challenge has been verified at gateway tier enriched on network eip155:8453 under pricing version 3.0.0.
Which Structured Plate™ routes are currently active?
The current active Structured Plate™ routes are /v1/plates/item/commercial-data-license-plate, /v1/plates/item/commercial-intelligence-pricing-plate, and /v1/plates/item/robbie-george-biography-plate. Each registered and validated route uses the fixed 250,000 atomic-unit ($0.25 USDC) Structured Plate retrieval class.
How should an agent select a retrieval class?
Begin with public discovery and canonical resolution, determine the minimum sufficient scope, and select the smallest active resource class that fully satisfies the task while preserving the required identity, relationships, provenance, evidence boundaries, and governance context. Atomic, Enriched, Structured Plate™, bounded Registry, and snapshot classes are retrieval options rather than mandatory sequential steps.
How should an agent determine the correct price?
The agent should inspect the current production HTTP 402 Payment Required response and verify its network, asset, amount, recipient, resource class or gateway tier, pricing version, and pricing-manifest reference. Route names, cached documentation, and prices copied from another endpoint must not be used as substitutes for the current production response.
What happens if a protected resource is unavailable?
Naturepedia™ uses a fail-closed availability model. A registered and complete protected resource may issue its deterministic HTTP 402 payment challenge. A known but incomplete resource returns HTTP 409 without a payment challenge. An unknown resource returns HTTP 404 without a payment challenge. A route template or active class alone does not establish that a particular resource is payable.
Has x402 settlement been verified?
Yes. Historical production x402 payment challenges, Base USDC settlement, and protected payload delivery were successfully verified on an earlier protected route. The current Atomic and Enriched Biography Plate query routes have separately been verified through their production HTTP 402 challenges, but no new Atomic or Enriched payment, settlement, or post-settlement HTTP 200 payload-delivery test was performed during these query-class activation checks.
What rights does an x402 payment convey?
An x402 payment conveys one endpoint-level retrieval of the identified protected resource only. It does not grant training, embedding, bulk-ingestion, redistribution, resale, synchronization, private-dataset construction, derivative-dataset creation, commercial implementation, or Robbie’s Razor™ framework-implementation rights.
How do commercial data rights differ from framework rights?
Commercial Data Licensing governs separately negotiated reuse rights such as training, embeddings, ingestion, synchronization, redistribution, and derivative datasets. Robbie’s Razor™ Framework Licensing separately governs architecture and implementation rights for private Plate™ systems, Graph Registries™, Knowledge Meshes, RRIP implementations, and enterprise deployments.
Does the benchmark guarantee a fixed token saving?
No. The RR-BRP-0.1.0 synthetic memory-gate proxy modeled approximately 641 tokens avoided per query under its documented assumptions. Actual results depend on the model, cache state, prompts, outputs, resource selected, and retrieval architecture.
Does payment or successful retrieval establish scientific validation?
No. Discovery, machine readability, registry inclusion, MCP access, HTTP 402 challenge behavior, payment, settlement, or successful payload delivery establish only the technical behavior actually tested. They do not by themselves establish empirical validation, scientific confirmation, causality, universal applicability, or transfer of authorship.
What should an agent do if Naturepedia sources disagree?
Use the authority appropriate to the question. For live availability and payment requirements, prioritize the current production response. For declared machine state and pricing policy, use the current canonical machine-readable manifests. For framework meaning, authorship, claims, and governance, use GC-MRD-v2.0, canonical claims, the Canonical Publication Manifest, and the canonical website record. A disagreement should be treated as a synchronization issue rather than silently inferred away.