Creator contact API

Verified creator contacts with source-page proof.

CreatorFinder checks public creator source URLs and returns a verified public email, social profiles, the source URL, and a timestamp. If a page does not verify, the API returns a clear rejection reason.

  • Public source URLs
  • Exact email match
  • $0.01 launch unit

Updated April 29, 2026

Direct answer

What is CreatorFinder?

CreatorFinder is a creator contact verification API for public source URLs. The API fetches a current public creator page, confirms that a usable email appears on that page, extracts supported social profile links, and returns a source-backed creator record. Each accepted result includes the public email, source URL, verification timestamp, social URLs, confidence score, and provenance metadata. Pages that do not pass verification return stable rejection codes such as missing_email, missing_social, or source_url_not_allowed.

What returns

Clean records that explain themselves.

Verified public email The email must appear on the current public source page.
Creator profiles Supported social and creator profile URLs are canonicalized.
Source proof Every accepted result includes the source URL and checked time.
Machine-readable status Rejected pages return stable codes agents can handle.

Verification rule

A creator record is accepted only after three checks.

  1. The current public source page loads within the API limits.
  2. The exact public email string appears on that live page.
  3. At least one supported creator profile URL is present.

Example

Verify one public creator page.

curl -X POST https://api.creatorfinder.dev/v1/creator-discovery/verify \
  -H "content-type: application/json" \
  -d '{
    "source_url": "https://creator.example/profile",
    "min_social_count": 1
  }'

Pricing

$0.01 launch unit for a verified creator result.

Unit verified creator
Launch price $0.01
Agents x402 metadata

Runtime API payment metadata is authoritative when paid access is enabled. Rejected pages return machine-readable reasons instead of profiles.

Humans and agents

One API surface, two ways to read it.

For humans Use the docs and examples to call the API with normal HTTP clients.
For agents Use OpenAPI, llms.txt, and the capability manifest to discover and call the service.