Registry-listed posture
A public registry listing and a dedicated MCP onboarding layer make the surface legible to both human buyers and agent builders.
Trust
Built for small, high-value intelligence tasks rather than broad platform sprawl
This MCP is designed to be credible in production-style agent workflows: narrow capability boundaries, stable machine-readable outputs, and budget-aware request posture.
Structured capability boundaries
Three flagship wrappers keep the commercial story narrow and the task surface easy to understand.
Budget-aware by default
x402-compatible per-request billing keeps machine usage measurable and predictable.
Confidence-aware outputs
Responses are shaped to expose source summary and confidence rather than hide evidence quality behind polished prose.
Why this is narrow by design
Why this is narrow by design
The product is intentionally built around a small number of high-value China tasks. That makes task selection, pricing, and orchestration easier than a sprawling endpoint catalog.
Structured outputs
Structured outputs
The response model favors machine-readable summaries, recommendation cues, and workflow metadata rather than narrative-heavy prose that needs to be re-parsed later.
Pricing and budget control
Pricing and budget control
Per-request x402 payment keeps the commercial model aligned with repeated agent use. Buyers can reason about task cost directly instead of mapping seat-based pricing onto workflow volume.
Execution classes
Execution classes
Some requests are direct and lightweight. Others are orchestrated wrappers that combine multiple underlying routes. The page system explains that behavior plainly without overclaiming deeper workflow features.
Evidence and source posture
Evidence and source posture
The system is designed to expose confidence and source-summary cues rather than pretend certainty where evidence is thin or mixed.
What this is not
A narrow product layer, not a maximalist platform claim
Not a giant horizontal data platform.
Not generic LLM browsing dressed up as a product surface.
Not a seat-based BI suite.
Not a raw route dump as the primary experience.