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.

A developer integrating the Easy2257 Partner API at a workstation

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

Storing government IDs (Easy2257 holds them; you store an account ID)
Responding to federal inspection requests (forward law enforcement to Easy2257)
Generating monthly acquirer reports (we generate per-producer, automatically)
Building a removal portal (we host it at easy2257.com/report/removal)
Tracking 48h / 72h / 7bd takedown SLAs (we track and alert)
Maintaining a 7-year retention guard (enforced at our DB layer)
Verifying performer ID + face match (handled on our infrastructure)
Building cross-reference indices (auto-generated as content is logged)

The integration is three calls

About 15 minutes for a backend engineer. Full reference in the docs.

Partner APIv1
  1. 1

    POST /api/v1/solo-accounts

    Onboard a creator. Returns an onboardingUrl and status pending_onboarding.

  2. 2

    WEBHOOK solo_account.verified

    Creator verified. Release the content you were holding.

  3. 3

    POST /api/v1/solo-accounts/:id/content

    Log each approved upload against the creator's record.

For platforms and developers

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.