Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.
openapi: 3.2.0
info:
title: ICME Preflight — Cryptographic Guardrails for AI Agents Top…
version: 1.0.0
description: 'ICME Preflight replaces model-based guardrails with formal verification and cryptographic proofs. Write policies in plain English — Preflight compiles them to formal logic (SMT-LIB) and checks every agent action with a mathematical solver. SAT = allowed, UNSAT = blocked. Every decision produces a zero-knowledge proof: tamper-proof, independently verifiable, and private. Docs: https://docs.icme.io'
guidance: 'Getting started: 1) POST /v1/createUserX402 with { username } to get a 402 with a USDC deposit address on Base. Send $5 USDC, then retry with { username, stripe_payment_intent_id } to complete signup. The response contains an api_key — save it. Use it as the X-API-Key header on all subsequent calls. You receive 325 starting credits. 2) POST /v1/makeRules with { policy } and your X-API-Key header — write your guardrail in plain English (up to 50 rules). Preflight compiles it to formal logic and returns a policy_id. Costs 300 credits. 3) Verify agent actions — two paths: (a) POST /v1/checkIt with X-API-Key header — costs 1 credit per call, use this if you already have credits from signup or topUp. (b) POST /v1/checkItPaid — x402 USDC payment per call, no API key or account needed, best for autonomous agents. Both accept { policy_id, action } and return SAT/UNSAT with extracted values and optional ZK proof. For a minimal ALLOWED/BLOCKED response, use POST /v1/verify (API key, 1 credit). Credit budget: signup gives 325 credits. makeRules costs 300, checkIt/verify cost 1 each. That leaves 25 checks after your first policy. When credits run out, POST /v1/topUpX402 to add more ($5 = 500 credits per x402 payment) ZK proofs: after calling checkIt/checkItPaid, wait a few minutes for proof generation, then POST /v1/verifyProof with the zk_proof_id to verify the cryptographic receipt. No extra cost — already covered by the original check. Single-use per proof. Tip: end every action string with an explicit claim and state all policy variables. Full docs: https://docs.icme.io/api-reference'
servers:
- url: https://api.icme.io
tags:
- name: TopUpX402
paths:
/v1/topUpX402:
post:
operationId: topUpX402
summary: Add 500 credits via x402 USDC payment ($5.00)
description: Pay $5.00 USDC on Base via x402 to add 500 credits to your account. Requires X-API-Key header to identify which account to credit. No request body needed.
x-payment-info:
protocols:
- x402
pricingMode: fixed
price: '5.000000'
responses:
'200':
description: Credits added — returns credits_added (500), credits_balance
'402':
description: Payment Required — pay $5.00 USDC on Base via x402
requestBody:
required: false
content:
application/json:
schema:
type: object
description: No body required. Requires X-API-Key header to identify the account to credit.
properties: {}
tags:
- TopUpX402