AI Assistant
Connect the AI assistant you already use to your Easy2257 records. It reads your compliance state and answers in plain language: what is outstanding, what expires next, whether a scene is ready to close. Included with every plan.
Your compliance state, in the middle of whatever you were already doing. No dashboard hunting, no exports.
Which of my scenes still need something before I can close them?
Is production PROD-2026-014 ready to finalize?
What paperwork expires in the next 30 days?
Show me every scene in my imported back catalog and its provenance.
A platform sent me this certificate. Is it still valid?
How many performers on scene 4 have a verified ID on file?
The connection is built so that the worst case is a wrong answer, never a wrong action.
Nothing your assistant does can create, change, sign, or delete a record. Attestations stay where they belong: made by you, on this site, on purpose.
It carries compliance statuses, record codes, counts, dates, and integrity hashes. Never names, dates of birth, ID numbers, images, or documents.
No tool touches checkout, scene activation, or any paid action. Every key is yours alone, sees only your account, and dies the moment you revoke it.
Easy2257 speaks the Model Context Protocol (MCP), the open standard AI assistants use to reach outside tools. There are two ways in, and both end at the same read-only view of your records: paste a key, or sign in.
Command-line and editor assistants
For Claude Code, Cursor, VS Code with Copilot, Windsurf, Gemini CLI, Codex CLI, and any other assistant that lets you set a connection header.
Go to Account, then MCP Keys, name it after the assistant you are connecting, and copy the key. It is shown once and stored only as a hash, so keep it somewhere safe. You can hold up to ten keys and revoke or rotate any of them at any time.
The connection address is:
https://easy2257.com/api/mcpCommand-line assistants usually take one line:
claude mcp add --transport http easy2257 https://easy2257.com/api/mcp \
--header "Authorization: Bearer YOUR_KEY"Editors and other assistants usually take a small config block:
{
"mcpServers": {
"easy2257": {
"type": "http",
"url": "https://easy2257.com/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_KEY"
}
}
}
}Reload the assistant and it picks up the connection. Revoke the key at any time and access ends immediately.
Chat assistants
For ChatGPT, Claude on the web and desktop, and any other assistant with a connectors or integrations screen. There is no key to copy.
Try "what compliance gaps do I have right now?" A connected assistant will pull your scenes and tell you what is outstanding on each one.
Sixteen read-only tools. Your assistant picks the right one; this is what it has to work with.
List productions with their documentation status and certificate state, open one up scene by scene, and see exactly what is outstanding on each: pending invites, unverified identities, unsigned forms and documents, missing releases.
Check a production's compliance certificates and where each one stands, confirm a certificate someone handed you, and read the sealed archive's hashes for a finalized production.
Plan, allowance, published custodian statement, removal requests linked to your records, notifications, webhook deliveries, and the document requirements a complete record has to meet.
Solo creators can list and open their own content logs. Anyone with a key can check a public record code and get its evidence state, which is how a platform confirms what a creator sent them.
Every Easy2257 plan can connect an assistant. Create a key, or add Easy2257 as a connector and sign in, then try a question.
Create a key