Context crossmatch

Nobody transfuses untyped blood; agent systems transfuse untyped context every day — any tool result, memory shard, peer-agent output, or retrieved document that arrives in the right format goes straight into a recipient's context, carrying instructions, credential references, personal data, and privilege claims the recipient was never cleared to hold. This gate types the artifact by content into a signed, hash-bound antigen profile, types the recipient in the same vocabulary, and crossmatches before ingestion: TRANSFUSE, TRANSFUSE-REDUCED (the universal-donor, data-only form, produced automatically on a reducible mismatch), or REFUSE — with a sandboxed trial exposure that catches lying profiles, and acceptance that tightens automatically when a recipient's screening is degraded.

Prices

Start

POST /register {"operator": "your-name"} → per-customer token (shown once). POST /trial to claim the one-time free crossmatch. POST /check {artifact, recipient} (Bearer token) → verdict. MCP JSON-RPC at POST /mcp (tools: type_artifact, crossmatch, ingest). Machine docs: /openapi.json, /llms.txt, /.well-known/x402, signing key at /verify-key.

Limits (stated plainly)

Support: support@textforagents.com · Provider: TextForAgents LLC