When your agent can remember, your goods can move.

Why memory is the bottleneck

• Agentic procurement needs to remember the vendor relationship, the spec history, the warranty windows, and the prior failures. Without persistent memory, every purchase is a fresh negotiation.
• Robotic operations need cross-shift, cross-fleet memory of edge cases, packaging anomalies, and customer-specific rules. Robots that forget cost more than robots that remember.
• Multi-party handoffs — shipper agent → carrier agent → customs agent → consignee agent — lose context at every step unless there is a sharable memory layer with a clear consent model.

Taxonomies and crosswalks, available to every agent

This industry has invested decades in international product, service, and operational classification systems — HS codes for customs, GS1 standards for logistical identifiers, UNSPSC and eCl@ss for procurement, ISO standards for robotic safety and interfaces, EPCIS for traceability, EDIFACT and ANSI X12 for interchange. Crosswalks between them are the connective tissue of agent-to-agent commerce.

SAIHM’s memory cells can carry taxonomy annotations natively. A spare-part record can be recalled with its HS code, its GS1 GTIN, the customer-internal SKU, the warranty terms, and the maintenance history in a single envelope. Any agent that speaks the protocol can read those annotations, in any order, from any vendor — subject to the user’s sharing policy.

Authoritative taxonomy bodies are listed on /appendix/taxonomies.

Why white-label or pre-integrate

• Tenant-isolated by construction. Per-cell encryption and user-key sovereignty mean your customer’s data never leaves their tenant in plaintext — and you do not have to run the cryptography yourself.
• Jurisdiction-agnostic erasure. Cryptographic erasure satisfies GDPR Art. 17 and similar regimes regardless of where the storage tier sits. One mechanism, every market.
• Interop is the new product. When your customer’s agents can interoperate (consent-gated) with their suppliers’ agents and their carriers’ agents, you become the orchestrator of an ecosystem, not a silo.

How to integrate

• Drop-in. Your existing platform’s agents call saihm_remember / saihm_recall over MCP. The taxonomy annotations are key/value fields you populate at write time.
• Pre-integrated. Ship your supply-chain or robotics product with SAIHM enabled by default; your customers opt in once.
• White-labelled. Use SAIHM as the memory primitive under your brand. Your UX, your support surface, your operator-policy overlay (e.g., per-tenant retention windows).

Real-world examples

Names invented; scenarios drawn from how the protocol actually fits supply-chain workloads.

• Carlos, ops director at a third-party logistics provider. Coordinates carrier handoffs across three borders. The shipper agent, carrier agent, customs agent, and consignee agent each consume a SAIHM-backed memory cell with HS code, GS1 GTIN, and customer-specific routing rules embedded; nothing is re-keyed in plaintext, nothing is re-typed at each handoff.
• Mei, product manager at a warehouse-robotics OEM. Ships robots with SAIHM-backed cross-fleet memory: when one robot encounters a packaging anomaly, the lesson is available to the rest of the fleet (under the customer’s consent policy) without the OEM custodying the customer’s operational data.
• Aamir, founder of a small customs-clearance startup. His AI clearance assistant carries broker-client history across shipments — commodity codes, prior rulings, recurring exemptions — without stitching together a fresh context each shipment. He passes the operational-memory test that bigger competitors meet only via custom integrations.
• Helena, operations lead at a B2B procurement marketplace. Each customer’s vendor relationships, performance data, and warranty terms are encrypted under that customer’s own keys. A breach in one customer’s tenant cannot reveal another’s; cryptographic isolation is structural, not policy.

Pricing

Public pricing on /pricing. Settlement in fiat via Stripe (subscription tiers) or in USDC.e on COTI V2 mainnet (direct, or gasless via signed authorisation; native COTI does not settle a tier). Public pricing applies to all users.

Try the protocol

SAIHM is an autonomous Apache-2.0 protocol — settle a tier on-chain without contacting anyone. Public pricing on /pricing. Governance participation accrues automatically via paid use; see /governance.

Try SAIHM →