For platforms and developers
Drop-in 2257 compliance,
by API.
Integrate the Partner API and Easy2257 becomes the Custodian of Records for your creators' content. Your platform never touches an ID. One call to onboard a creator, a webhook when they are verified, one call to log each upload.
What you're actually on the hook for
UGC platforms in the adult space don't get a pass on these. They each impose distinct obligations directly on you, separate from your users' producer obligations.
18 U.S.C. § 2257 secondary producer
28 CFR 75.1(c)(2): any platform that publishes, reproduces, or manages explicit UGC may be a secondary producer with its own ID record-keeping obligation. Penalty: up to 5 years imprisonment.
Mastercard AN 5196
Adult Content Merchants must collect documented written performer consent and maintain a depicted-person removal appeals process. Failure triggers acquirer review.
Visa VIRP
Tier-1 Adult Merchants must submit a monthly compliance report to their acquirer (nil reports too) covering removal SLAs, signed releases, and verifications.
TAKE IT DOWN Act (2025)
Federal NCII removal mandate: 48-hour SLA for taking down reported content. Easy2257 monitors and alerts on breach so you don't blow the deadline.
Easy2257 covers all four, by API, in one integration.
What you stop doing
The integration is three calls
About 15 minutes for a backend engineer. Full reference in the docs.
- 1
POST /api/v1/solo-accounts
Onboard a creator. Returns an accountId, an onboardingUrl, and status pending_id_verification.
- 2
WEBHOOK solo_account.verified
Creator verified. Release the content you were holding.
- 3
POST /api/v1/solo-accounts/:id/content
Log each approved upload against the creator's record. Idempotent on your own externalContentId, and it takes an optional SHA-256 of the file.
- 4
GET /api/v1/solo-accounts/:id
Current status, and a FRESH onboardingUrl when onboarding is incomplete and the old link has expired. Onboarding tokens live 7 days, so this is what a "finish your compliance setup" banner calls.
- 5
WEBHOOK solo_account.suspended
The account stopped being compliant, usually a lapsed subscription. Revoke upload access. If it is restored and the ID verification is still on file you get solo_account.verified again, with no second onboarding trip for the creator.
Before you write the integration
- Provisioning is idempotent. Calling POST /api/v1/solo-accounts twice with the same internal user ID returns the existing account, so it is safe on every login.
- There is no sandbox, and only live keys are accepted: every v1 endpoint writes a real compliance record, and a fake one is worse than none. New partner accounts start with a test key, so creating the live key is genuinely the first task.
- Rehearse with your own mailboxes: run one pass end to end, watch the webhook land, then delete the content you logged. Every rejected call still shows in the partner dashboard request log, so a misconfigured key is visible rather than silent.
- Multi-performer productions go through the Collab Scenes API: create a scene with a list of performers and each one gets their own link to verify identity and sign a release, without seeing anyone else's documents. The scene publishes on collab_scene.greenlit.
- Each finished production carries an RS256-signed compliance certificate that verifies offline against our JWKS endpoint, so an inspector or an acquirer's auditor can check it without calling our API.
Hand off 2257
in one integration.
One integration covers 2257 record-keeping, card-network rules, and takedown SLAs. Read the docs or talk to us to start.