Experience cross-system participation history. Sign in, get a sandbox API key, submit events, resolve identities — see what happens when multiple participants share the same history layer.
No account needed. Use the public sandbox key below to submit events and evaluate policies right now.
Set this in your terminal once:
export YOUR_SANDBOX_KEY="mir_sandbox_public_2026"
This is a shared public key. Events are isolated to the sandbox and don't affect production data.
Sign in for a dedicated sandbox key with your own event history.
Record a participation event. Pick a user and event type, then hit Submit. The event is recorded instantly.
curl -s -X POST https://mir.events/v1/events \
-H "Content-Type: application/json" \
-H "x-api-key: $YOUR_SANDBOX_KEY" \
-d '{
"userExternalId": "user_alice",
"eventType": "transaction.completed",
"occurredAt": "'$(date -u +%Y-%m-%dT%H:%M:%S.000Z)'"
}' | jq
Ask MIR whether an actor should be allowed to perform an action. The response is based on their actual participation history.
curl -s -X POST https://mir.events/v1/policy/evaluate?debug=true \
-H "Content-Type: application/json" \
-H "x-api-key: $YOUR_SANDBOX_KEY" \
-d '{
"actor": {
"id": "user_alice",
"type": "human"
},
"action": "iam.grant_admin"
}' | jq
Claims are attributed assertions about negative behaviors (chargebacks, suspensions, policy violations). They are recorded and surfaced but do not affect tier calculations. Consuming partners decide what claims mean for their context.
curl -s -X POST https://mir.events/v1/claims \
-H "Content-Type: application/json" \
-H "x-api-key: $YOUR_SANDBOX_KEY" \
-d '{
"userExternalId": "user_alice",
"claimType": "claim.chargeback"
}' | jq
After submitting a claim, run a policy evaluation on the same user. You'll see the claimStatus field change from clean to flagged or contested, and high-risk actions may be denied.
Recent sandbox activity across all participants.