API · MCP · Apify

Creator emails for your code and your agents.

One lookup, three ways in. Every response carries the source URL, so your agent can show its work.

In preview. Join the list for early keys.

REST

One endpoint.

Send a channel link, @handle, channel ID or video link. Get back the email, where it came from, and its status. Misses cost nothing and return every source checked.

POST /v1/lookup

{ "channel": "@northtrailfilms" }

{
  "channel_id": "UC…",
  "email": "press@northtrail.co",
  "source": "channel_description",
  "source_url": "https://youtube.com/@northtrailfilms/about",
  "checked_at": "2026-10-22T14:03:00Z",
  "confidence": "high",
  "status": "verified",
  "charged": true
}

MCP

Ask your assistant for creator emails.

A remote MCP server with OAuth for Claude, ChatGPT and Cursor. Ask for a channel's business email and get the answer with its receipt, inside the chat.

Example prompts

Find the business email for @northtrailfilms and show the source.
Look up these 40 channels and give me a CSV of the verified ones.
Which of these creators publish a manager email instead of their own?

Apify

Already on Apify?

The same lookup as an Apify actor, charged per email found. Use it from Apify's console, its API, or its MCP server.

Same data

Identical fields and sources as the Endcard API.

Per email found

No charge for channels without a published email.

Limited permissions

Built to run with the minimum access Apify allows.