claude mcp add --transport http scrapefield https://scrapefield.com/mcp
GET/v1/google-maps/places
3 credits
Search Google Maps for businesses and places
const params =newURLSearchParams({"query":"coffee shops in Brooklyn"});const res =awaitfetch(`https://api.scrapefield.com/v1/google-maps/places?${params}`,{
headers:{ Authorization:`Bearer ${process.env.SCRAPEFIELD_KEY}`},});const{ data, meta }=await res.json();
console.log(data, meta.credits_charged);
// press Send — you get back an array of google_maps_place,// every field present, null where the platform shows nothing
Clean JSON, named like the official APIs
Every response is structured JSON with a documented schema. Google Maps data uses the field names from Google’s Places API, Instagram data the names from the Instagram Graph API, TikTok data the names from TikTok’s API, and X data the names from X’s API v2. If you have used those, you already know most of ours.
Every field documented, with its type.
The same fields in every response, even when empty.
Each endpoint has a fixed price in credits, listed on the pricing page. Buy credits once and spend them on any platform. If a request fails, the credits go back to your balance automatically.
A fixed price per endpoint, shown in every response.
A call to google-maps/place timed out, so it cost nothing. Its credits were back before you noticed.
GET linkedin/profile−11
GET google-maps/places−3
GET google-maps/place0 · refunded 3
Google Maps
5 endpoints · from 3 credits
Places API names
LinkedIn
18 endpoints · from 3 credits
LinkedIn’s labels
Instagram
6 endpoints · from 3 credits
Graph API names
TikTok
8 endpoints · from 3 credits
TikTok API names
X
8 endpoints · from 3 credits
X API v2 names
Refundedjust now
3 credits returned
A call to google-maps/place timed out, so it cost nothing. Its credits were back before you noticed.
GET linkedin/profile−11
GET google-maps/places−3
GET google-maps/place0 · refunded 3
01
02
Built for agents, not just for people
A growing share of “which API should I use” is settled inside a coding agent. Every layer that reader needs is here, and all of it is generated from the definition the API runs on — so none of it can drift from what the API does.
Every endpoint has a published credit cost — 3 credits for a Google Maps place, 3 for an Instagram or TikTok profile, 11 for a LinkedIn profile. Multiply by your volume and that is your bill. The number does not depend on how long something took, how much memory it used, or whether we happened to have it cached. A call we fail is refunded automatically, and the reversal appears in your usage ledger rather than in a support ticket.
Why only five platforms?
Every platform takes constant work to keep running, and we publish a success rate for each endpoint. So we add a platform only when we’re sure we can keep it reliable. YouTube, Reddit and Facebook are next.
What happens when a platform changes and something breaks?
Our status page says so before you have to ask, and calls that fail are not charged. Where we can, a surface is served by more than one source, so a problem with one is invisible to you — the response shape does not change either way.
Do credits expire?
No. There is no plan, so there is no billing period for them to expire at the end of — credits you buy stay bought. There are also no discount codes, no twenty-eight-tier plan ladder and no per-seat pricing. The price on the pricing page is the price.
Can I use this from an AI agent?
Yes — that is what it is built for. There is an MCP server with the same endpoints as tools, an OpenAPI spec of every data endpoint, and an llms.txt an agent can read in one fetch. The MCP server has a demo mode that works with no key at all.