Agent IAM — Now in Early Access

The control plane for
autonomous AI agents

Your agents are authorized, scoped, and every action is in an auditable hash-chained log. Flip agents from liability to asset — built to withstand the EU AI Act.

Get Access See how it works
What IronWeft does

Everything your agents need to be trusted

One API. Every control your autonomous agents need — from registration to retirement.

🪪

Agent Identity

Every agent gets an Ed25519 keypair and a cryptographic ID. Full provenance — every action traceable back to a human sponsor, always.

🔑

Scoped Credentials

Short-lived JWTs with embedded scopes. payments:write can't call data:delete. Credentials expire. Stolen keys go stale before they can be used.

⚖️

Policy Authorization

Every action runs a policy check before it executes. Allow, deny, or challenge. Configurable per tenant — JSON rules today, OPA tomorrow.

🔗

Hash-Chained Audit Log

Append-only, tamper-evident audit trail. SHA-256 chained from the first event. Regulators ask — you produce.

🧵

Delegation Chains

Human → agent → sub-agent. Scopes only flow down, never up. Suspend one node and the whole chain is denied.

🚨

Auto-Suspend

3 consecutive denies within 60 minutes trigger automatic suspension. Configurable per tenant. Hard lock at 5+.

🛡️

IP Allowlist

Even a leaked API key is useless from an unauthorized IP. Lock your integration to specific CIDRs — tenant self-serve, CIDR-aware, no support ticket needed.

🔔

Webhooks

Your agents can't go rogue without you knowing immediately. Instant notification on every deny, challenge, suspend, or retire event — 3 retries, exponential backoff.

🔍

Initiator Tracking

Every action records who triggered it — a user, a script, or another agent. Full attribution across your entire integration, immutably hash-chained. Enforce it tenant-wide.

🏛️

EU AI Act Risk Tiers

Risk tier classification built in at registration — not bolted on. High-risk domains flagged, prohibited uses blocked at the gate. Compliance evidence on demand.

Your agent acted at 3am.
Can you prove it was authorized?

You can. That's credential lifecycle management.

Fintech
Healthcare
Customer-facing
Without IronWeft

An agent initiates a $2,400 transfer at 3am. Your ops team investigates.

$ grep -r "payment" logs/ 03:14:22  payment_initiate  $2,400 03:14:23  success $ #  ... that's all you have
Was this action authorized?
What permissions was it running with?
Which human is accountable?
Which script or user triggered this?
Has this agent done this before?
Can you prove the log was not altered?
Is the credential still active?
Is this agent still running?
vs
With IronWeft

Same scenario. Pull the audit trail. Answers in seconds.

$ curl ironweft.io/audit?agent_id=agt_4ae283ac | jq "decision": "allow" "sponsor": "user_m_chen" "scope": "payments:write" "chain_valid": true
Authorized — policy check logged at 03:14:21
payments:write only — nothing else
Sponsored by user_margaret_chen
Triggered by script:billing_runner — full initiator chain
2 prior actions on record, both authorized
SHA-256 chain intact — unaltered
JWT expired directly after task completion
Agent auto-suspended after 3 consecutive denies
Without IronWeft

An agent queries patient records for 847 individuals during a routine workflow run.

$ grep "patient_data" logs/ 14:32:11  patient_data_query  847 records 14:32:12  success $ #  ... that's all you have
Was the query within authorized scope?
Which patient cohort was accessed?
Which clinician is accountable?
What triggered the query?
Was this volume expected or anomalous?
Can you prove the log was not altered?
Is the credential still active?
Can you prove HIPAA compliance on demand?
vs
With IronWeft

Same query. Pull the audit trail. HIPAA evidence ready in seconds.

$ curl ironweft.io/audit?agent_id=agt_7bc491df | jq "decision": "allow" "sponsor": "user_r_patel" "scope": "phi:read" "chain_valid": true
Authorized — policy check logged at 14:32:10
phi:read only — write and delete blocked
Sponsored by user_dr_rachel_patel
Triggered by workflow:care_coordinator
Scope bound to cohort_id:c4f2 — nothing else accessible
SHA-256 chain intact — unaltered
Credential expired after workflow completion
HIPAA audit export ready on demand
Without IronWeft

An agent sends 3,200 promotional emails on behalf of your sales team.

$ grep "email_send" logs/ 09:15:44  email_send  3,200 recipients 09:15:45  success $ #  ... that's all you have
Was the send authorized?
Which list segment was targeted?
Who approved this campaign?
Which automation triggered it?
Was the suppression list honored?
Can you prove the log was not altered?
Is the credential still active?
Can you produce GDPR consent evidence?
vs
With IronWeft

Same send. Pull the audit trail. GDPR evidence exportable on demand.

$ curl ironweft.io/audit?agent_id=agt_2da804bc | jq "decision": "allow" "sponsor": "user_k_torres" "scope": "comms:send" "chain_valid": true
Authorized — policy check logged at 09:15:43
comms:send only — contacts:write blocked
Sponsored by user_kim_torres
Triggered by script:campaign_q2_runner
Suppression list enforced at credential scope
SHA-256 chain intact — unaltered
Credential scoped to campaign_id:q2-promo only
GDPR consent evidence exportable on demand
Developer-first

Three API calls to full agent accountability

Works like Stripe. One API key, REST endpoints, a 5-minute integration.

Register
Authorize
Audit
# 1. Register an agent
curl -X POST https://ironweft.io/agents \
  -H "Authorization: Bearer iw_live_xxx" \
  -H "Content-Type: application/json" \
  -d '{
    "agent_name": "Grace",
    "sponsor_id": "user_margaret_chen",
    "initial_roles": ["call_agent"]
  }'

# Response
{
  "agent_id": "agt_4ae283ac96dd4b40",
  "public_key": "ed25519:272741c6...",
  "status": "active"
}

# 2. Before your agent acts — authorize it
curl -X POST https://ironweft.io/authorize \
  -H "Authorization: Bearer iw_live_xxx" \
  -d '{
    "credential": "<short-lived JWT>",
    "action": "call_initiate",
    "resource": "+1-555-0100"
  }'

# Response
{
  "decision": "allow",
  "audit_event_id": "evt_a1b2c3d4"
}
Audit trail

Every decision. Tamper-evident. Forever.

Provenance on demand. Each event is SHA-256 chained to the previous one — delete or alter any row and the chain breaks. Regulators ask, you produce.

0000...0000 agent registered allow
a3f8b2c1d4e5... call_initiate allow
9d2e7f0c1b3a... payment_initiate $750 challenge
4c1a8e3f2d0b... payment_initiate $1500 deny
7b0f3c9e1a2d... auto_suspended suspended
Open source SDKs

Five-minute integration in any language

Raw HTTP or SDK — your choice. All three are open source, zero external dependencies, and wrap the same REST API.

🐍

Python

pip install ironweft

Decorator pattern, typed exceptions, httpx-based. One dependency.

github.com/ironweft/ironweft-python →
📦

Node.js / TypeScript

npm install ironweft

Zero runtime dependencies, native fetch, full TypeScript types. Node 18+.

github.com/ironweft/ironweft-node →
🐹

Go

go get github.com/ironweft/ironweft-go

Standard library only, context-aware, idiomatic error types. Zero external deps.

github.com/ironweft/ironweft-go →
Pricing

Pay for what your agents do

Pay per authorization. Nothing more. Scale from prototype to production without repricing.

◆ 10 of 10 founding slots remaining
Starter
$0 / month
1,000 authorizations included
 
Up to 3 agents
Full audit trail
API access
Community + docs support
Enterprise
Custom
$0.0008 – $0.002 / auth
 
Everything in Pro
Negotiated volume pricing
Direct support
Estimate your monthly cost
Authorizations / month 10,000
1k100k200k300k400k500k
Starter
$0
up to 1,000 auths
Growth
$49 founding
$99 standard · $0.003/auth
Pro
$199 founding
$299 standard · $0.002/auth
Enterprise
Custom
negotiated volume pricing
Growth is your best fit at this volume

Founding pricing — locked for life, non-transferable

First 10 teams lock in founding rates forever — no rate hikes, no plan changes. Growth at $49/mo + $0.003/auth, or Pro at $199/mo + $0.002/auth. Standard pricing takes over when slots fill.

10 of 10 founding slots remaining Standard: Growth → $99/mo · Pro → $299/mo.
Claim Founding Slot →
In Production
Built on IronWeft
EverHomeCall

EverHomeCall delivers scheduled AI-powered calls to people who benefit from regular check-ins — seniors, independent living, injury recovery, and remote caregivers. Every call is authorized through IronWeft before it reaches a recipient's phone. Zero unauthorized calls by design. Full audit trail on every decision.

Read the integration story →
Compliance

Built for regulated environments

Controls and audit evidence your legal, security, and compliance teams can act on — without asking engineering to build it from scratch.

Tamper-evident audit trail

Every agent action is SHA-256 chained to the previous event. Modify or delete any record and the chain breaks — cryptographic proof of what happened and when.

Scoped credentials

Agents receive JWT credentials scoped to specific permissions with configurable TTLs. No agent can act outside its granted scope, even if compromised.

Policy engine

Declare what agents are allowed to do in code. Every action is evaluated at runtime — no policy match, no action. Policies are versioned and auditable.

Access controls

IP allowlisting, API key rotation, and webhook alerts on every security event — deny, suspend, retire. No custom access-control code required.

Audit export on demand

Pull your full audit trail via API at any time. Every event includes agent ID, action, outcome, timestamp, and chain hash in JSON or CSV.

No data training

IronWeft never uses your agent data, actions, or audit events to train models. Your operational data stays operational.

Framework alignment
EU AI Act — Art. 12 audit requirements GDPR-aligned HIPAA-ready

Compliance review? forged@ironweft.io — we respond within 1 business day.

Ship compliant agents
before August 2026.

The EU AI Act requires provable audit trails for high-risk AI systems. IronWeft is that infrastructure — integrate now, prove compliance on demand.

Claim Founding Slot →