The Enrichment API for Clay — All Sources, One Key

LinkedIn profiles, company data, email finder, Twitter, Instagram, Google Maps, and more — all accessible via a single API key in Clay's HTTP API column. One credit per record. No charges for failed lookups.

1 credit per record, not per field No charges for failed lookups Sculptor AI auto-configures Clay One API key for every source

Four Reasons Clay Teams Switch Their HTTP Columns to Anysite

1 credit per record, not per field

Clay's built-in enrichments charge per data point. An Anysite LinkedIn call returns the full profile — headline, experience, company, skills, connections — for 1 credit. You map as many fields as you need from the response. No incremental charges per field.

No charges for failed lookups

If a LinkedIn profile doesn't exist or is private, you get a 404 response. You are not charged for requests where the record cannot be found. With Clay's built-in waterfall, credits can be consumed by providers that fail to find data.

Sculptor AI auto-configuration

Anysite's AI Data Agent can generate the full HTTP API column configuration — endpoint URL, request body, field mapping, error handling — for your specific Clay workflow. Available on all paid plans.

One API key for every data source

Connecting LinkedIn, email finding, company data, and Twitter to Clay via HTTP API columns normally means managing multiple API keys. Anysite consolidates all of these under one key and one billing cycle.

The Real Value

Anysite isn't just another enrichment vendor. It turns any public website into a structured API. LinkedIn, company sites, Google Maps, Crunchbase, YouTube, Twitter, Instagram, Reddit — all accessible via one API key, all with the same credit model. When your Clay workflow needs a new data source next month, you don't buy another API. You use an endpoint you already have.

Authentication

All Anysite API requests use the access-token header. There is no OAuth flow, no SDK, no client initialization — every call is a plain HTTP POST.

Header format
POST https://api.anysite.io/api/linkedin/user
access-token: ak_live_xxxxxxxxxxxxxxxxxxxx
Content-Type: application/json

Getting your API key: Sign up at app.anysite.io → Dashboard → API Keys → Generate New Key. Production keys begin with ak_live_.

Key rotation: Rotate every 90 days or immediately if exposed. Generate the new key before revoking the old one to avoid downtime on running Clay tables.

Connect Anysite to Clay in Under 20 Minutes

1. Get your Anysite API key

Sign up at app.anysite.io. Navigate to Dashboard → API Keys → Generate New Key. Copy the key.

2. Open your Clay table

Navigate to the Clay table where you want enrichment. Add Anysite alongside existing columns or replace an expensive one.

3. Add an HTTP API column

Click “+ Add Column” → select “HTTP API”. This is Clay's built-in column type for external API calls.

4. Configure the endpoint

Enter the Anysite endpoint URL, method (POST), and headers. See the sample configs below.

5. Map the input

In the Body field, reference your Clay column that holds the LinkedIn URL or email. Use Clay's column syntax: .

6. Map the output fields

Clay extracts specific JSON fields from the response and maps them to table columns. Each field comes from the same single API call.

7. Test on a single row

Before running on your full table, test on one row to verify the response.

8. Run on full table

Once the single-row test passes, run the enrichment on your full table. Monitor credit usage in the Anysite dashboard.

Copy-Paste Configurations

LinkedIn Profile Enrichment

POST https://api.anysite.io/api/linkedin/user

Request body
{
  "url": ""
}
Response schema
{
  "urn": "urn:li:person:ABC123xyz",
  "first_name": "Jane",
  "last_name": "Doe",
  "headline": "Head of Revenue at SaaSCo",
  "location": "Austin, TX",
  "connections": 847,
  "experience": [...],
  "education": [...],
  "skills": ["Salesforce", "HubSpot"]
}

Credit cost: 1 credit per record

Company Data

POST https://api.anysite.io/api/linkedin/company

Request body
{
  "url": ""
}

Credit cost: 1 credit per record

Email Finder

POST https://api.anysite.io/api/linkedin/user/email

Request body
{
  "urn": ""
}
Response
{
  "email": "jane.doe@saasco.com",
  "confidence": 0.94,
  "source": "professional"
}

Credit cost: 1 credit per successful lookup. No charge if email is null.

Google Maps Local Business

POST https://api.anysite.io/api/ai_based/google_maps/search

Request body
{
  "query": " "
}

Credit cost: 1 credit per record

Rate Limits and Concurrency

PlanRequests per minuteSafe Clay parallelism
Starter60Up to 5 concurrent rows
Growth90Up to 7 concurrent rows
Scale150Up to 10 concurrent rows
Pro200Up to 15 concurrent rows
429 response
HTTP/1.1 429 Too Many Requests
Retry-After: 8

{
  "error": {
    "code": "rate_limit_exceeded",
    "message": "Rate limit exceeded. Retry after 8 seconds.",
    "retry_after": 8
  }
}

Clay's HTTP API column retries 429 responses automatically. If the rate is consistently exceeded, reduce Clay's per-column parallelism.

Error Taxonomy

HTTPerror.codeMeaningCharged?Action
400invalid_parameterBad parameter type or valueNoFix request — check param field
401invalid_keyAPI key missing or revokedNoRegenerate key in dashboard
402insufficient_creditsAccount has 0 creditsNoPurchase top-up or upgrade plan
404record_not_foundProfile/record not found or privateNoExpected for private profiles — map as “not found” in Clay
422unprocessable_entityInput could not be resolvedNoVerify input format
429rate_limit_exceededToo many requests per minuteNoBack off per Retry-After
500upstream_errorPlatform returned errorNoRetry with backoff
200SuccessYesExpected behavior — null fields mean no data available

How Anysite Compares

Anysite Apollo.io Datagma Findymail
Pricing modelCredit-based, 1/recordSubscription + per-exportPer-recordPer-email
LinkedIn profilesYes — full profileLimitedYesNo
Email finderYesYesYesYes (primary)
Company dataYes — detailedYesYesNo
Twitter/X profilesYesNoNoNo
Instagram profilesYesNoNoNo
Google MapsYesNoNoNo
Crunchbase dataYes (20 credits)NoNoNo
All sources one keyYesApollo data onlyLimitedEmail only
Starter price$49/mo$49+/mo~$50+/moUsage-based
Failed lookup chargesNoYes (usage counted)VariesYes

Competitor pricing and features as of April 2026. Verify current details directly with each provider.

Simple Pricing for Any Enrichment Volume

PlanPrice/moCreditsRate Limit
Starter$4915,00060 req/min
Growth$200100,00090 req/min
Scale$300190,000150 req/min
Pro$549425,000200 req/min
Enterprise$1,199+1.2M+200 req/min

PAYG top-ups: $2.90 per 1,000 credits on any active plan. Top-up credits roll over for 12 months. Starter includes a 7-day free trial with 1,000 credits.

What 15,000 Starter Credits Buys

Credits are consumed per API call, not per field. How many records you get from 15,000 credits depends on which endpoints your workflow uses:

Enrichment type Credits per record Records at $49/mo
Basic LinkedIn profile115,000
Full LinkedIn profile (with experience, education, skills)4–91,700–3,750
Email finder (successful lookup)115,000
Company data by domain115,000
Twitter profile115,000
Instagram profile115,000
Google Maps business115,000
Crunchbase record20750

Note: Failed lookups don't charge. Most common SDR workflow (LinkedIn URL → full profile) averages ~4 credits per record.

Recommended for active SDR teams: Growth plan at 100,000 credits/month covers most mixed-endpoint workflows comfortably.

Frequently Asked Questions

How does credit accounting work for Clay enrichment?
Each standard Anysite endpoint call costs 1 credit. One API call to /api/linkedin/user returns the full LinkedIn profile. You map as many fields as you need from each response — adding more field mappings in Clay does not increase credits. Crunchbase costs 20 credits per call.
What are the rate limits and how do I handle them in Clay?
Starter plan: 60 requests per minute. If Clay enrichment exceeds this rate, Clay receives 429 responses with a Retry-After header. Clay retries automatically. For 10,000+ row runs, configure column parallelism per the rate limits table above.
Does Anysite retry failed lookups automatically?
Anysite retries transient failures (rate limits, temporary unavailability) internally before returning an error. If a LinkedIn profile doesn't exist, Anysite returns a 404 immediately and is not charged.
Does Anysite support Clay webhooks or is it request-only?
The HTTP API column in Clay is request-only — Clay calls Anysite synchronously per row. Anysite returns data in the HTTP response. There is no webhook or async callback.
How fresh is the LinkedIn data?
Anysite retrieves data in real time at the point of the API call. There is no cached data served from a database. The data reflects what is publicly visible on LinkedIn at the moment of extraction, subject to a brief propagation lag of a few minutes.
Can I switch to Anysite for some columns but keep Clay's built-in for others?
Yes. You can use Anysite HTTP API columns alongside Clay's built-in enrichment columns in the same table. A common pattern is to use Clay's email verification features while using Anysite for LinkedIn and company data.
What if I need a data source Anysite doesn't cover?
Anysite's AI-powered parser (/api/webparser/parse) can extract structured data from any URL. For dedicated endpoint coverage requests, contact hello@anysite.io.

One API key for every Clay enrichment column

15,000 credits per month on Starter. 7-day free trial, no credit card required. Full API documentation at docs.anysite.io.