Platform roadmap and development status

This page documents work already explored in the local prototype and the remaining steps. It is not a delivery schedule or a paid-service offer.

Discovery and comparison

The local prototype includes lexical search with curated aliases and availability/budget filters. A development MCP tool interface was explored. The deployed service exposes service JSON and OpenAPI; it does not currently expose a public MCP server or multi-service discovery endpoint.

Quotes, orders and verification

The local platform explored maximum-budget quotes, SQLite-backed orders, idempotency, input-bound quotes, owner/session separation and integrity receipts. Quality checks, queue leases, retry fencing and scoped credential handling also exist as development components. Their integration and production security are not established by local module tests.

Provider routing

The local DNS adapter explored fallback on provider errors with bounded attempts. Future routing must preserve input constraints, authorization and budgets. Only Crossref DOI retrieval is currently active on the public backend.

Payment experiments

The prototype explored x402 authorization and testnet USDC on Base Sepolia. A test attempt reached service execution but encountered a settlement failure; completed on-chain payment was not demonstrated. Simulated ledger and testnet balances are not revenue. Mainnet payments, public checkout, reconciliation and refund handling are not available.

Requirements before a commercial launch

• A useful capability and a specific buyer need, with measured delivery cost.
• Production client isolation, authorization and recovery tests.
• Reliable payment reconciliation, retry rules and refunds before charging.
• Defined provider rights, limits, retention, backup and support policies.

Priorities can change with evidence. No launch date or price is promised. Review capability status.