Axiom Pilot Program Agreement

1. Parties

This Pilot Agreement ("Agreement") is entered into as of the date of last signature ("Effective Date") between:

Axiom Inc., a Delaware corporation ("Provider"), and the entity identified in the Stripe checkout record associated with this pilot ("Customer").

2. Scope of Services

Provider shall provide Customer with access to Axiom's cryptographic execution receipt infrastructure for the Customer's internal AI agent skill invocations via MCP (Model Context Protocol), for a period of ninety (90) calendar days from the Effective Date.

Services include:

• API access to Axiom's receipt generation endpoint (POST /api/receipts/invoke)
• Unlimited receipt generation during the pilot period
• Access to the public receipt verification endpoint (GET /api/receipts/:id/verify)
• One (1) production AI agent skill instrumented with cryptographic receipts
• Open-source verifier (MIT license, zero dependencies) tested by Customer's team
• Founder Slack and email support during business hours
• 30-minute kickoff call + day-30 midpoint check-in

Deliverables at pilot end: (i) at least one live skill producing signed execution receipts in Customer's production environment; (ii) Customer's compliance team independently verifying receipts using the open-source verifier, without Provider assistance.

Regulatory alignment. Axiom's execution receipt architecture is designed to address the following compliance obligations — Customer's compliance team can verify alignment independently:

• EU AI Act Art. 12 & 13 — Axiom receipts provide the per-invocation audit logs and transparency artifacts required under high-risk AI system recordkeeping obligations. Each receipt contains: skill name, timestamp, SHA-256 input hash, SHA-256 output hash, HMAC-SHA256 signature, and verification status.
• SOC 2 CC7.2 — Cryptographic receipts satisfy the monitoring of system components requirement; the Merkle-root audit bundle supports point-in-time export for auditor review.
• HIPAA §164.312(b) — Audit control standard. Signed execution receipts provide tamper-evident records of AI agent activity across covered entity workflows, with no raw PHI stored by Provider (only SHA-256 hashes).

Nothing in this Agreement constitutes legal or compliance advice. Customer remains solely responsible for its own regulatory obligations.

3. Price and Payment

Payment confirms acceptance. Submitting payment via the Stripe checkout link constitutes Customer's acceptance of this Agreement. No wet signature required. Provider will issue an API key and schedule the kickoff call within 2 minutes of payment clearing.

Refund policy. Pro-rated refund for unused days if Provider terminates before day 75. No refund if Customer terminates after day 15.

4. Success Criteria

By the end of the 90-day pilot, Customer will have demonstrated the following:

Meeting these criteria constitutes successful pilot completion. Failure to meet criteria due to technical blockers attributable to Provider will extend the pilot period by mutual written agreement. The pilot is complete when all three criteria are satisfied or when the 90-day period ends, whichever comes first.

5. Customer Commitments

In exchange for pilot access, Customer agrees to:

• Case study participation: Provide logo, company name, and 2–3 quotes about the experience (redactable at Customer's discretion). Provider may use in marketing materials pending Customer's written approval of final copy.
• Reference call: Participate in up to one (1) reference call with a prospective Axiom customer, scheduled by mutual agreement within 60 days of pilot end.
• Feedback sessions: Attend structured feedback sessions at day 30, day 60, and day 90 with Provider's founding team.

6. Data Handling and Intellectual Property

Customer Data. Customer's AI agent invocation inputs and outputs are processed within Customer's isolated tenant. Raw data never leaves Customer's tenant in plaintext. Only SHA-256 hashes are stored server-side. Provider has no access to Customer's invocation content.

Receipts. Execution receipts generated by Axiom are owned by Customer. Provider may store hashed copies for verification durability purposes only.

Provider IP. Axiom's product, including its cryptographic signing architecture, verification infrastructure, and SDK, is and remains the exclusive property of Provider. Customer receives a limited, revocable license to use the product during the pilot.

Aggregated Analytics. Provider may use anonymized, aggregated pilot metrics (e.g., total receipts generated across all pilots) for product improvement and sales materials — never identifying individual Customer data.

7. Termination

Either party may terminate this Agreement with thirty (30) days' written notice (email sufficient). Upon termination by Provider before day 75: pro-rated refund of unused pilot days. Upon termination by Customer after day 15: no refund. Provider may terminate immediately for material breach by Customer (including non-payment or unauthorized redistribution of product).

Upon termination, Customer's API key will be revoked. Receipts generated during the pilot remain verifiable via the public verification endpoint indefinitely.

Post-pilot wind-down: If Customer does not renew after the pilot, access continues for 30 days after pilot end date with no further obligation.

8. Out of Scope

The following are explicitly excluded from this Agreement unless agreed in a separate written statement:

• Custom integrations with Customer's internal systems beyond standard MCP SDK support
• SLA commitments beyond best-effort response times (post-pilot SLA available as a separate commercial agreement)
• Guaranteed uptime or availability SLAs during the pilot
• Legal or compliance advice regarding Customer's specific regulatory obligations
• Warranties beyond what is documented in the public trust page at /trust

9. Definitions