Production-grade context feeds. Built for agents. x402-native.

What it is

A context feed productized for autonomous consumption.

ShoDhen Context is the agent-tier product in the ShoDhen family. It exposes the same refined-intelligence substrate that powers ShoDhen Gnosis and ShoDhen Counsel for human readers -- but rendered structured, streamable, and priced for machine consumption.

Context is consumed by AI agents, not by humans. The buyer is the agent itself. Payment is autonomous, settled per-token over the x402 protocol -- the HTTP 402 Payment Required pattern, instrumented for stablecoin micropayments. There is no monthly subscription, no seat license, no human in the purchase loop.

Architecturally, Context sits upstream of your vector store and downstream of raw web scraping. It is the refined layer: editorially curated, deduplicated, sourced, structured. Think Bloomberg Terminal feeds for finance terminals -- generalized to the broader knowledge economy, and addressed to agents instead of analysts.

For whom

AI engineers shipping agents that need real context.

ShoDhen Context is for the engineering teams whose agents have outgrown raw retrieval.

You're an AI engineer building an autonomous workflow that needs daily-fresh, editorially refined context -- and you've discovered that scraping is brittle, that public APIs rate-limit you into uselessness, and that your vector store is only as good as what you put into it.

You're a developer designing M2M payment flows and you want a real x402 endpoint to integrate against -- not a sandbox, not a demo, a production feed your agent can actually buy from.

You're an enterprise AI team that needs structured-data context with predictable per-token economics and a service-level commitment, not a free tier that disappears.

Context is built for engineers in those positions. Documentation is technical, pricing is metered, and the integration shape is whatever your agent already speaks.

How it works

x402, stablecoin, per-token. Standard HTTP, native to the agent.

Context implements the x402 protocol end-to-end. The mechanic:

1. 1. Request

   Your agent issues a standard HTTP request to a Context endpoint (GET /v1/feeds/feed_id or similar).

   GET /v1/context?topic=fintech-regulation&window=24h&lens=competitor

2. 2. 402 Payment Required

   The endpoint returns HTTP 402 Payment Required with a payment challenge in the response headers -- feed identifier, token quote, accepted stablecoins, settlement address.

   HTTP/1.1 402 Payment Required
   X-Payment-Required: usdc,1.42,base,<nonce>

3. 3. Auto-pay

   Your agent's wallet -- running as a sidecar, a signer service, or an embedded key -- auto-pays the quoted amount in the chosen stablecoin. Settlement is on-chain; confirmation is sub-second on the supported L2s.

   GET /v1/context?topic=fintech-regulation&window=24h&lens=competitor
   X-Payment: <signed-payment-proof>

4. 4. Refined context payload

   The agent retries the request with a payment-proof header. The endpoint returns the refined context payload -- JSON, streaming JSON, or NDJSON, agent's choice.

   200 OK
   Content-Type: application/json
   {
     "schema": "sodhen.context.v1",
     "topic": "fintech-regulation",
     "lens": "competitor",
     "window": "24h",
     "refined_at": "2026-05-18T14:00:00Z",
     "signals": [ ... ],
     "sources": [ ... ]
   }

Pricing is per token consumed on the returned payload, not per request. Long payloads cost more than short ones; identical re-fetches in a cache window are free.

Integration surface area. Context ships with first-class adapters for LangChain (Python and TS), the Model Context Protocol (MCP server), OpenAI Assistants connectors, and a direct HTTP API for anything else. The reference implementation is a single file in your agent's runtime.

The shared substrate

One substrate. Two reader types. Three products.

ShoDhen Gnosis and ShoDhen Counsel are the human-readable surfaces of a refined-knowledge editorial substrate -- sources monitored, claims verified, lenses applied, structure imposed. ShoDhen Context exposes that same substrate to a different reader: the agent.

The economic shape matters. Content-engineering investment is the dominant cost in this business, and it amortizes across reader types. The same editorial pass that produces a Gnosis briefing and a Counsel briefing produces a structured, machine-addressable feed that an agent can consume autonomously. One substrate, three products, three reader markets -- candidate, operator, agent.

For the developer, the consequence is simple: the feed you integrate against is the feed that human professionals are paying real money to read. It is refined upstream of you. Your agent inherits that refinement at the token level.

Pricing

Per-token. Stablecoin. Free credit to start.

Per-token consumption over x402. Final rates are finalizing in a pricing experiment with design-partner integrations; the public benchmark is competitive with prevailing LLM context-window pricing (OpenAI and Anthropic input-token rates as the reference band).

No subscriptions. No seat licenses. Your agent pays, in tokens, for what it consumes.

Status

Ships after Counsel. Design partners onboarding now.

ShoDhen Context is the heaviest engineering lift in the ShoDhen family and is sequenced to ship after ShoDhen Counsel -- public availability is targeted for the period following Counsel's public release. The x402 settlement layer, the editorial-to-feed pipeline, and the adapter surface area are all in active build.

The design-partner program is open now. Selected partners receive early endpoint access, a direct line to the engineering team, free stablecoin credit for integration testing, and locked launch pricing on production usage. The program is sized intentionally small to keep the feedback loop tight.

FAQ

Questions engineers ask before integrating.