Nau mai, haere mai
INATE™ gates backend execution on the INATE™ Hearts sequence: a timed tap pattern completed upstream, before the payload commits, bound to the exact action and verified at the boundary.
> POST /api/v1/bridge/payload/lock · one call from your backend
The INATE™ Hearts sequence: a timed tap pattern read upstream, at the execution boundary, before your backend commits. Try the live demo →
A new category of technology: Intentional Coherence™. A human’s decision, physical gesture, and the backend payload, locked in cryptographic alignment at the exact moment an action occurs.
Stored API keys work for whoever holds them.
MFA checks the login, not the payload it commits hours later.
Logs record what executed, never who approved it.
INATE™ moves the proof upstream. No human, no commit.
Your backend registers the intent payload with INATE™ and gets back a lock ID.
The user completes the Hearts sequence. INATE™ returns an IVA Token and a signed receipt.
Your backend validates the receipt. Verified, it runs. Tampered, missing, or forged, it’s dropped.
What the user completes: the timed Hearts tap, at the moment of commit, bound to the exact payload and recorded in the signed receipt.
Explore iPAS →What your backend enforces: the receipt rules that gate execution. INATE-signed, in-window, payload-matched, single-use, or the commit is refused.
Read the architecture →INATE Powered™ → iPAS → the Hearts sequence. No valid receipt, no commit.
POST /api/v1/bridge/payload/lock
Authorization: Bearer inate_live_••••••••
Content-Type: application/json
{
"action_id": "act_8f9a01b2",
"payload_hash": "e3b0c44298fc1c14…",
"callback_url": "https://yourco.com/hooks/inate"
}presence"verified"
payload_hash"e3b0c44298fc1c14…"
decided_at"2026-09-04T09:41:07.312Z"
signature"Mx4hR8vQ…" · Ed25519
Usage-based. No minimum, no commitment — pay only for verified approvals, billed monthly.
Start now
Card required; charged only for usage. Then connect your backend and gate your first action.