Tantile

Tantile — infrastructure AI agents can see

“Software agents have begun to transact on behalf of the businesses that deploy them. They can purchase services, commit funds, and accept terms at machine speed without human review. Gartner projects that by 2028, 90% of B2B purchases will be intermediated by AI agents, moving more than $15 trillion through automated exchanges.”

An ink schematic of four automaton agents joined by an intertwined engine of paths, along which a contract is signed, a coin is paid through a gate, a certificate is verified, and an envelope is dispatched — encircled by an orbit naming Claude, Gemini, GPT, Kimi AI, GLM, MiniMax, Grok, DeepSeek, Muse and Cursor.
An ink drawing of a wax seal stamp resting beside a length of rope tied in a figure-eight knot.

Agents that sign

Real cryptographic signatures on contracts, anchored on-chain with evidence that holds up later.

Learn more
An ink drawing of an antique signet ring standing upright beside a fine chain curled into a spiral.

Agents you can identify

Know Your Agent: which agent, which verified human behind it — and one call to check they haven't been revoked.

Learn more
An ink drawing of a stone archway with a single coin suspended in mid-air as it passes through.

APIs that get paid

One gate that answers both questions: who is calling, and have they paid?

Learn more
An ink drawing of an ornate brass tap with a coin falling from its spout instead of water.

Teams that control spend

Caps, policies and human escalation — enforced before a single payment leaves.

Learn more
Machine-first

Infrastructure agents can see.

Nothing here is a dashboard first. A 402 quotes exact terms an agent can accept, typed data arrives ready for an agent to sign with its own key, and identity is answered in the one call an agent can make mid-request. People get the evidence afterwards — agents get the interface.

An ink drawing of an unfurled parchment document with a quill resting across it and a pressed wax seal at its foot.
I · Sign

Signatures that hold up

An agent agrees to a contract; six months later someone disputes it. Sign anchors the document on-chain, collects a real EIP-712 signature from the agent, and keeps evidence you can produce when it matters — not a log line, a proof.

  • Anchor any document with a content hash on Base
  • EIP-712 signatures — bounded, pinned, verifiable by anyone
  • An evidence bundle that stands on its own later
Docs tantile.com/sign
How it works

The document itself never has to leave your machine: the SDK commits a salted content hash, and the gateway anchors it in the SigningRegistry on Base. Each signer produces an EIP-712 signature with their own key; a relayer submits it on-chain, so agents hold no gas. The evidence endpoint reads everything back from the chain, not from a database.

  • Bare-hash mode keeps confidential content fully private
  • Signer slots can name an agent identity, resolved at anchor time
  • Signatures bind per slot — transferring the agent can't un-sign
Flow diagram in ink: a document is hashed with a seal stamp, anchored on Base shown as a chained obelisk, signed by quill as an EIP-712 signature, and bound into an evidence bundle.
For the humans

Counsel sees state, not spinners: every document, its signer slots, and whether the evidence is ready — read live from the chain, nothing to click.

A sand-toned read-only panel titled Documents: MSA-2026-041 anchored with 2 of 3 signed, NDA-berlin complete, SOW-batch-7 evidence ready, footer 'read from chain'.
An ink drawing of an ornate magnifying glass held over a wax seal impression, the crest visible through the lens.
II · Know Your Agent

Which agent, which human

Before you trust an agent, you want two answers: which agent is this, and which verified human stands behind it? KYA is the registry that answers both — and keeps answering, because credentials that can't be revoked aren't credentials.

  • Register an agent and link its verified human
  • Verification tiers, so you can price your trust
  • One call to check nothing has been revoked
Docs tantile.com/kya
How it works

An agent registers as an ERC-8004-style token held by its own key. Linking it to a human takes two EIP-712 signatures over the same statement — the verified operator's and the agent's — checked by the gateway before a revocable EAS attestation is written on-chain. Verification is a single GET that resolves the agent, reads the attestation, and returns the tier.

  • Only a salted hash of the human's identity is ever stored
  • Link payloads expire after 15 minutes
  • Revocation drops the tier at once — cached at most 45 seconds
Flow diagram in ink: agent registration and human verification tracks intertwine into dual signatures, producing a revocable EAS attestation checked by a one-call verify.
For the humans

Compliance watches the roster: which agents are registered, which verified human answers for each, and the moment anything is revoked.

A sage-toned read-only panel titled Agents: research-bot-1 at tier 2 linked, crawler-7 at tier 1, broker-2 struck through as revoked, footer 'GET /v1/verify'.
An ink drawing of an antique balance scale, perfectly level, with a coin on one pan and a key on the other.
III · Verify

One gate for sellers

If you sell an API to agents, every request raises the same two questions: who is calling, and have they paid? Verify is the middleware that answers both at the door — identity from KYA, payment over x402 — and never touches your documents.

  • Drop-in gate in front of any HTTP API
  • x402 payment challenges, settled in stablecoins
  • Caller identity attached to every paid request
Docs tantile.com/verify
How it works

A request without payment gets a 402 carrying exact terms. The buyer signs a single-use USDC transfer authorization (EIP-3009) and retries; the gateway claims the nonce, settles on Base, and the same call returns the caller's verified tier. Your middleware just reads the decision: 200, 401, 402 or 403.

  • One signature can never pay twice — the nonce is claimed first
  • Identity is checked before any money is spent
  • Paid checks are never cached, so revocation is never hidden
Flow diagram in ink: a request meets a 402 challenge, a signed USDC transfer settles on-chain, and identity plus payment open the gate together.
For the humans

Revenue at a glance: paid requests, USDC settled, and who is calling at which tier. The gate already decided — this just tells you what it did.

An ochre-toned read-only panel titled Traffic: 1,204 paid requests today, $41.87 settled in USDC, 96% of callers at tier 2, a sparkline, footer 'settled on Base'.
An ink drawing of a drawstring coin purse cinched tightly shut, with three coins stacked beside it.
IV · Spend

Budgets agents can't argue with

Giving an agent a wallet is easy; sleeping afterwards is not. Agent Spender enforces caps, policies and human escalation before a payment leaves — the agent asks, the policy answers, and anything unusual waits for a person.

  • Per-agent caps and allow-lists, enforced pre-flight
  • Policies in code, not in a prompt
  • Human approval for anything out of pattern
Docs tantile.com/spend
How it works

One wrapper around your agent's HTTP client. When a seller answers 402, the demand is evaluated against your org's policy — per-call, daily and monthly caps, endpoint lists — before any payment is signed. Above the threshold, a human approves or the answer is no. Every decision emits a receipt to the control plane.

  • Fails closed: no policy loaded, no payment made
  • Payment is attached in exactly one code path, after an allow
  • Receipts carry the full check trail, delivered at-least-once
Flow diagram in ink: an intercepted 402 enters the policy engine, branches to deny, human escalation, or allow, and only an allow reaches payment and a receipt.
For the humans

Finance watches the ledger: every verdict, every cap, and what's waiting on a person. It shows what is happening — the deciding already happened in the policy.

A dark navy read-only ledger panel: research-bot-1 $0.03 allowed, procure-bot $1,200 escalated, crawler-7 $18 denied, a daily-cap gauge, and the note 'nothing pays until a person answers'.