AI Assistant

Ask your assistant what is missing.

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.

Create a keySee the setup

Things producers ask it

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 PROJ-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?

Safe to point at your records

The connection is built so that the worst case is a wrong answer, never a wrong action.

It only reads

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.

No performer identity

It carries compliance statuses, record codes, counts, dates, and integrity hashes. Never names, dates of birth, ID numbers, images, or documents.

It cannot spend money

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.

Two minutes to connect

1. Create a key

Go to Account, then API 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.

2. Point your assistant here

The connection address is:

https://easy2257.com/api/mcp

Command-line assistants usually take one line:

claude mcp add --transport http easy2257 https://easy2257.com/api/mcp \
  --header "Authorization: Bearer YOUR_KEY"

Editors and desktop assistants usually take a small config block:

{
  "mcpServers": {
    "easy2257": {
      "type": "http",
      "url": "https://easy2257.com/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_KEY"
      }
    }
  }
}

Works today with any assistant that lets you set a connection header, including command-line and editor assistants. One-click sign-in, which some chat assistants require instead of a key, is on the way.

3. Ask it something

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.

What it can look at

Sixteen read-only tools. Your assistant picks the right one; this is what it has to work with.

Productions and scenes

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.

  • list_productions
  • get_production
  • get_scene_compliance
  • list_compliance_gaps
  • list_expiring_documents

Certificates and archives

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.

  • get_certificate
  • verify_certificate
  • get_archive_status

Your account

Plan, allowance, published custodian statement, removal requests linked to your records, notifications, webhook deliveries, and the document requirements a complete record has to meet.

  • get_removal_requests_summary
  • get_account_status
  • list_notifications
  • list_webhook_deliveries
  • get_compliance_requirements

Solo creators and public codes

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.

  • list_content_logs
  • get_content_log
  • verify_record

Included with your plan

Every Easy2257 plan can connect an assistant. Create a key and try a question.

Create a key