Vendor-neutral AI playbook for authenticating to Herodotus Cloud programmatically with an EVM wallet (EIP-712 → Bearer access token → API key). Required precondition for every Herodotus API skill.
AI SkillsUse this playbook when an AI assistant or CLI needs to authenticate to Herodotus Cloud programmatically using an EVM wallet — exchanging an EIP-712 challenge for a Bearer access token, then retrieving an API key.This is the first skill to load for any non-browser Herodotus integration: the Atlantic, Storage Proof, Data Processor, and Satellite skills all assume an API key is already in hand.
The full wire protocol: GET /auth/web3/challenge → sign EIP-712 → POST /auth/web3/session (with channel: "bearer" in the JSON body) → GET /api-keys → POST /auth/refresh-token.
Channel-binding semantics — why a Bearer-issued JWT must never be presented via cookie (and vice versa).
A bring-your-own-signer model: the protocol is signer-agnostic. The reference example uses viem; KMS, hardware wallets, MetaMask, and ethers all work without changing the skill.
Anti-hallucination guardrails: do not invent endpoints, do not hardcode the EIP-712 domain/types/statement, do not assume a default projectId.