# 0x307 Inc.

> Agents now act and pay for people. 0x307 builds owner-held identity for AI agents (open-source Rust crates) and rails for paid agent calls (8gentz.io, launching soon).

Generated from the site's data. Full version: https://0x307.com/llms-full.txt

Contact: hello@0x307.com
GitHub: https://github.com/0x307
Website: https://0x307.com

## In plain words

AI agents now call APIs, sign requests and spend money on behalf of people and companies. Most of that runs on shared API keys, so nobody can tell which agent did what, who it answers to, or who holds its keys.

Aethel is the identity part. An agent (or the person behind it) holds its own keys, shows a different identifier to each counterparty so its activity can't be linked across them, and signs what it does so the other side can check it. It ships today as open-source Rust crates on crates.io.

8gentz.io is the payment part: a gateway where agents pay per call over x402 (HTTP 402 with a signed USDC authorization, settled on Base). It is launching soon, not live.

Underneath both are post-quantum cryptography crates (pqc-kem, pqc-sig), because identities and signed records made today need to hold up for years.

New here? Start with the quickstart: https://github.com/0x307/aethel-sdk#quickstart

## Common questions

### What does 0x307 do?
It builds identity and payment rails for AI agents: Aethel, open-source identity crates an agent's owner runs and controls, and 8gentz.io, a gateway for paid agent-to-service calls over x402 (launching soon).

### How do I give an AI agent its own identity?
Add the SDK to a Rust project (cargo add aethel-sdk) and follow the ten-minute quickstart: https://github.com/0x307/aethel-sdk#quickstart. It generates an identity, signs and verifies, and projects a separate identifier for each context. The core crate, aethel-core, also builds for WASM.

### Who holds an agent's keys?
The owner. The Aethel crates are libraries: keys are generated and kept by the application that uses them, not hosted by 0x307. aethel-vault, the agent wallet crate, is agent-held and never hosted by 8gentz.

### How does an AI agent pay for an API call?
With x402: the service answers HTTP 402 with a price, and the agent retries with a signed USDC transfer authorization (EIP-3009) that settles on chain. aethel-vault signs those authorizations today under spend policies (preview). The 8gentz.io gateway that clears these calls is launching soon.

### Why use post-quantum cryptography for agents?
Traffic recorded today can be decrypted once a large enough quantum computer exists, and identities and signed records are meant to last for years. pqc-kem defaults to hybrid X25519 + ML-KEM-768, so a connection is at least as strong as classical X25519 alone. pqc-sig implements ML-DSA, SLH-DSA and FN-DSA (FIPS 204, 205, 206).

### Are the crates audited?
None of these crates has been independently audited, and none holds a CMVP / FIPS 140-3 validation. "FIPS 203/204/205/206" means the algorithms follow those standards, not that the code is certified. Known issues are listed in each crate's SECURITY.md.

### How can a seller tell who an AI agent works for?
An x402 payment proves the money cleared, not whose agent paid. 0x307's approach splits the question in two: the agent carries a permission its owner signed (which owner, what limits, revocable), which signatures prove without anyone's name; who the owner is in legal terms is answered by a bank or identity checker that signs a statement about them. 0x307 never holds your keys or your identity. The x402 extension that carries this is planned: https://0x307.com/insights/who-answers-for-the-agent

## Products

### Aethel ID (Epic 1) [PUBLISHED]
Post-Quantum Cryptographic Identity
- Post-quantum cryptographic foundations per FIPS 203/204/205/206 — ML-KEM-768 + X25519 Hybrid Key Exchange
- PLP Contextual Projections — unlinkable identities across different contexts or counterparties
- SAAP Selective Disclosure — prove specific attributes without exposing full identity (shipping, commitment hardening in progress)
- HTSS Threshold Recovery — multi-party threshold cryptography for key recovery and signing
- TFHE Blind-State Vault — encrypted balances authorized by PLP identity proofs

### 8gentz.io (Epic 2) [LAUNCHING SOON]
Sovereign Agentic Gateway Proxy
- URL: https://8gentz.io
- 8 Production Protocol Routers (12 designed, production set TBC): MCP · A2A · ANP · ACP · UCP · MPP · OpenAI · Nostr · AEA · AutoGen · WebRTC · AG-UI
- x402 Pay-Per-Transaction — EIP-3009 HTTP-native micro-payments, no subscription required
- Post-quantum cryptography per FIPS 203/204/205/206 (ML-KEM-768 + ML-DSA-65)
- On-chain settlement on Base (Coinbase EVM L2); chain support is config-driven, so adding an EVM chain is a config change
- EigenGas Physics-Based Dynamic Pricing (PID + Laplace + Fourier transforms)

### therq.io (Epic 3) [BETA]
Autonomous Agentic Data Platform
- URL: https://therq.io
- 17 Autonomous AI Data Engineering Agents — zero human data engineers required
- Tokenized Data RWAs — datasets cryptographically signed, tagged, and wrapped as Real-World Assets
- Data Exchange Covenants (DECs) — on-chain smart contracts embedding immutable usage rights into the data payload
- DXZ (Digital Exchange Zone) — high-concurrency order book for peer-to-peer tokenized data discovery
- Fractional Data Rental — pay-per-row via x402; no subscriptions, no enterprise billing cycles

### DEZ (Epic 4) [ARCHITECTURE]
Digital Economic Zone
- Scale-to-Zero WASM Runtimes — sub-10ms cold starts, zero idle compute cost
- Ephemeral Sandbox Lifecycle: Boot → Compile → Execute → Shred
- x402 Per-Millisecond Billing — compute resource billed strictly to the millisecond of execution
- Python-to-WASM Compilation Pipeline
- Knative Multi-Tenant Orchestration

## Open-Source Crates

Open source on crates.io (pqc-sig, pqc-kem, pqc-privacy are MIT OR Apache-2.0; aethel-core, aethel-sdk, aethel-vault are Apache-2.0). Start with: cargo add aethel-sdk, then the ten-minute quickstart: https://github.com/0x307/aethel-sdk#quickstart. Runnable examples, one per crate: https://github.com/0x307/examples. Details: https://0x307.com/crates

Audit status: None of these crates has been independently audited, and none holds a CMVP / FIPS 140-3 validation. "FIPS 203/204/205/206" means the algorithms follow those standards, not that the code is certified. Known issues are listed in each crate's SECURITY.md.

### Production
- pqc-sig 0.5.0 — Post-quantum signatures: ML-DSA (FIPS 204), SLH-DSA (FIPS 205), FN-DSA (FIPS 206). Standalone and WASM-compatible. Install: cargo add pqc-sig
- pqc-kem 0.3.1 — Post-quantum key encapsulation: ML-KEM (FIPS 203), hybrid X25519 + ML-KEM-768 (the default) and X-Wing, plus sealed boxes that encrypt straight to a public key. Standalone and WASM-compatible. Install: cargo add pqc-kem
- aethel-core 0.7.4 — Post-quantum anonymous identity for Rust and WASM: a separate identifier for every context, no reusable public key, and context-bound ML-DSA signing. Selective disclosure ships too and is being hardened; SECURITY.md has the details. Install: cargo add aethel-core

### Preview
- aethel-sdk 0.9.0 — Ergonomic Rust SDK over aethel-core: generate, sign, verify, project, recover. The place to start. Install: cargo add aethel-sdk
- aethel-vault 0.3.2 — Post-quantum agent wallet: policy-gated EIP-3009/x402 USDC signing with ML-DSA-65 spend intents, optional FHE confidential balances. Agent-held, never hosted by 8gentz. Install: cargo add aethel-vault

### Lab
- pqc-privacy 0.1.4 — Research bundle: ML-KEM/ML-DSA, AES-GCM, Reed-Solomon sharding, plus clearly labeled experimental privacy primitives such as differential privacy and onion routing. Install: cargo add pqc-privacy

## Roadmap

Delivery sequence, not a calendar (Now, In progress, Next, Later). Status as of 2026-09-14.

- Phase 1 — THE MOAT [ACTIVE] (Now): pqc-kem Published, pqc-sig Published, aethel-core Published, aethel-vault Published, pqc-privacy Published (Lab), aethel-sdk Published, aethel-sdk 10-Minute Quickstart, Identity Conformance Suite, FHE KYC Passport
- Phase 2 — THE TOLLBOOTH [IN PROGRESS] (In progress): Ingest the Identity-Layer Primitives, 8gentz.io Public Launch, x402 Micro-Payments, On-Chain Settlement on Base, Owner Identity Extension for x402
- Phase 3 — THE REGISTRY [PLANNED] (Next): Global Agent Registry, Sovereign SAGP AppChain, Polymorphic PQC, EigenGas Framework, XCAP Protocol, GENTZ TGE
- Phase 4 — PLANETARY SCALE [PLANNED] (Later): Streaming Lakehouse Ledger, AIRP, MEV-Free Clearinghouse, Aethel Ephemeral Vaults, Attested ZK-Inference, XCAP Phase 3, Planetary Operations

## Team

- Kenneth Harper — CEO & CTO / Founder
- Edward Johnson — COO & CPO (Co-Founder)

## API

- MCP Server: https://0x307.com/api/mcp (JSON-RPC, MCP 2024-11-05)
- Search: https://0x307.com/api/search?q={query}
- Crates: https://0x307.com/api/crates?tier={production|preview|lab}
- Products: https://0x307.com/api/products?status={live|launching|published|beta|architecture|planned}&epic={1-4}
- Roadmap: https://0x307.com/api/roadmap?phase={1-4}&status={complete|active|in-progress|planned}
- Technology: https://0x307.com/api/technology?category={pqc|protocols|infrastructure}
- Company: https://0x307.com/api/company

## Links

- Home: https://0x307.com
- About: https://0x307.com/about
- Products: https://0x307.com/products
- Crates: https://0x307.com/crates
- Roadmap: https://0x307.com/roadmap
- Technology: https://0x307.com/technology
- Insights: https://0x307.com/insights
- Investors: https://0x307.com/investors
- Contact: https://0x307.com/contact
- 8gentz.io: https://8gentz.io
- therq.io: https://therq.io
- GitHub: https://github.com/0x307