Glasser

Provided by Apify

YouTube Creator Business Email

$0.18 per resultruns asynchronously — poll the Run

Find the business email address of a YouTube creator from a channel handle, URL or channel ID: one row per channel whose email was found, with the channel name, id, subscriber count and country. Up to 10 channels per call; you pay only for channels that return an email. A channel with no row is unconfirmed, not proven to have no email. The pinned Apify Actor returns at most 10 records through a durable Provider Job.

How to run it

Step 1Set up

Once: paste this into your agent's chat. The Skill installs the CLI and logs in by itself. For an agent that cannot use a shell, connect it over MCP instead.

Set up
set up https://glasser.ai/SKILL.md

Show me how to use the Apify endpoint /dataovercoffee/youtube-channel-business-email-scraper on Glasser.

Step 2Try a specific example task

When you need to assess a potential creator partnership, you might compare a channel’s available information with your collaboration criteria.

Copy this prompt into your agent to review a channel for a potential collaboration.

Prompt
Use apify:/dataovercoffee/youtube-channel-business-email-scraper on Glasser.
Research this channel against my collaboration criteria using only returned information.

Endpoint structure

json
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "channels"
  ],
  "properties": {
    "channels": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 500,
        "minLength": 1
      },
      "maxItems": 10,
      "minItems": 1
    }
  },
  "additionalProperties": false
}

How pricing works

Per result returnedCharged for each result returned. No charge when no data is returned.$0.18
Maximum per RunThe total charge will not exceed this amount.$1.80
Provider errorThe Provider failed to answer.$0.00
Timed outThe Run exceeded its time limit.$0.00
Internal failureAn internal error prevented completion.$0.00
Method POSTVersion 1Provider documentation ↗