Changelog
What changed
New features and changes to the API and the dashboard, newest first.
MCP server for AI agents
Connect Claude, Cursor, VS Code or your own agent to your organization at mcp.openshield.dev/mcp, under your own role.
- Sign in from the agent with OAuth, pick the organization and approve what it may do: read, moderate, or change fraud data, one scope at a time.
- Tools to read the organization, usage, decisions, keys, workflows, fraud cases, rules and lists, and to search the docs.
- Moderate a text or an image from the agent, billed like any check.
- With writes allowed, resolve a fraud case, edit list items and snooze rules; each action is in the audit log.
- The AI agents page: the address and setup for each client, who may connect, the connected agents with a disconnect button, and the call log.
- API keys take an MCP server scope, for an agent that cannot sign in through a browser. Such a key only reads.
Key activity and status
See what an API key does right now, what it used, its last calls, and what needs attention.
- Open a key's activity from the dashboard: its requests this minute, and your organization's requests, running checks and quota against its limits.
- The key's checks, fraud calls and cost this hour, over 24 hours and over 30 days, and its last calls from the journal.
- The key list flags a key that expires within 14 days, one in a rotation's grace period, one never used, and one idle for 30 days.
Edit an API key
Change an active key's name, scopes, workflows or expiry without replacing it.
- Edit an active key from the dashboard: its name, its scopes, the workflows it may use and its expiry. The key itself does not change, and the new access applies within seconds.
- A key stays in its environment, and an expired or revoked key cannot be edited.
- Owners and admins edit any key; developers edit the keys they created. Each edit is in the audit log.
Fraud prevention (beta)
A second product: score sign-ups, logins and payments with your own openfraud instance, under /fraud/v1, with the same API keys.
- Turn fraud prevention on in the dashboard: your organization gets an openfraud instance of its own, and its data never mixes with anyone else's.
- POST /fraud/v1/decide before a sensitive action, and /fraud/v1/events to report what happened. A decision costs EUR 0.001 and an event EUR 0.0002, from the same balance.
- API keys take a fraud scope: the whole fraud API, or decide and events only.
- Rule packs for free tiers and trials, cards and payments, messaging, marketplaces, APIs and hosting. Every pack rule starts in shadow until a person promotes it.
- From your first top-up, the network data: the operator and country of each address, and the lists of disposable email domains, Tor exits, data centres and VPNs.
- Webhooks for decisions and cases, signed with the Standard Webhooks scheme under a secret of your own.
- A free organization's instance is paused after 30 days without a call; the next call or a click in the dashboard resumes it.
- An attempt before sign-in (a failed login, a password reset) never acts on the account its email address belongs to, and an event your page reports is marked "reported_by": "client" so it names no account. Challenge outcomes count only from your server.
- Your instance keeps events, decisions and cases 30 days until your first top-up and 90 days after; the sandbox keeps them 30 days. Each instance gets the memory its options need, so turning on the network data or activity bursts never slows it down.
- Fraud lists are read item by item in the dashboard and the API; the CSV export of a whole list is withdrawn.
- The network data and the activity bursts now add to the price of a decision while they are on (EUR 0.0002 and EUR 0.0005): they hold more in your instance's memory. The dashboard shows the surcharge next to each one.
- The overview shows your limits and what the next top-up raises, instead of a plan: there are no plans any more, only a balance. The key and workflow limits still follow what you topped up in 30 days. Billing lists every limit level, what unlocks it and how much more reaches the next one.
Beta preview
The first version of openshield, ready to try.
- Prepaid use, with no subscription: top up a balance from EUR 5 and each check costs the components its workflow uses. Every account gets EUR 2.00 of free use each month. Automatic top-ups, a monthly limit on them, and email alerts on a low balance or a month's use.
- An advanced reading once you have topped up: a text sent to review gets a second, deeper reading, with the context you send.
- Check images and texts with POST /v1/image and POST /v1/text. The SightEngine workflow paths are there too, to make a migration easy.
- Every account gets the full answer: the decision, the reasons, and the score and threshold of each.
- Workflows set a review and a reject threshold per category. Add categories of your own and compare versions. Each workflow shows what it costs per image and per text before you save it.
- A decision journal with filters, details and export, and usage charts by day, key and workflow.
- Request limits rise with your top-ups, and every top-up has its invoice in the dashboard.
- Teams with roles, and two-factor authentication with an authenticator app, which owners turn on before their first top-up.