Volume quotes
Price follows expected monthly volume and which endpoints dominate the mix. If the first pack is mostly integration, say so — we price the live run.
Enterprise
Volume pricing, invoicing, and diligence.
Social Fetch is a public-data ingestion layer: we fetch posts, profiles, comments, and metadata through a stable API, and your product keeps the intelligence, scoring, and client UI. Enterprise means commercial and procurement help on the same live API as self-serve — no sales floor, no required demo.
- 99.8%
- API uptime · 90d
- 98.4%
- Request success
- ~3.2s
- Avg response
- ~500
- In-flight guidance
Uptime is availability — whether Social Fetch answered. Request success is completed lookups without an infrastructure failure. Neither is a contractual SLA. Full definitions.
Who this is for
Teams that already know they need a fetch layer.
Not a listening suite, and not a first conversation to invent the use case.
Vendor switch
Replacing an incumbent
Your listening or scraping vendor was acquired, repriced, or is sunsetting access. You need a drop-in acquisition layer, not a new analytics suite.
Embedded
Embedding data in your product
Brand protection, creator marketplaces, KYB and risk, or social intelligence you already sell — with procurement in the loop.
Always-on
Continuous coverage
The same entities, brands, or owned accounts, every day, across networks. Credits don't expire, so evaluation volume isn't a write-off.
What's included
Procurement and volume, on the same API.
Invoicing
For roughly 1M+ credits, or whenever procurement needs an invoice instead of card checkout. EU buyers: VAT documentation on request.
Security questionnaires
We answer specific data-handling questions. Practices, DPA, and subprocessors are already public — start there, then ask what's missing.
Concurrency review
No account-wide quota on paid routes — credits are the meter. Email the traffic shape if you expect sustained load above about 500 in flight.
What this isn't
- No named account executive, and no required demo before you can call the API.
- No SOC 2 or ISO 27001 certification — we say so plainly, and ask you to say if it's a hard gate.
- No contractual uptime SLA on standard terms — custom availability terms need a separate agreement.
How it works
From first request to volume quote.
Docs first, email second, sales last.
01
Test on free credits
Same live endpoints production uses. Verify lookupStatus, the { data, meta } shape, and requestId on failures.
02
Send the sketch
Endpoints, monthly volume, traffic shape, invoice needs. One email — we reply with specifics within a business day.
03
Get a number
A volume quote against your mix, questionnaire answers with doc references, and cutover notes if you're switching vendors.
Diligence
The procurement pack is already public.
No NDA required to read. Questionnaires welcome after you've tested the routes.
FAQ
Questions we get from procurement.
How much concurrency can I send?
Paid routes are not gated by an account-wide concurrency quota — credits are the meter. For stable production traffic, keep fewer than about 500 requests in flight. Sustained load above that is fine to plan for; email the endpoint mix and the traffic shape so we can say whether that pattern will hold.
Does Social Fetch have SOC 2?
No, and we do not hold ISO 27001 either. The product is public social data through our API; we never take social-account passwords. Current practices are on /security, with /dpa and /subprocessors for procurement. If a certification is a hard vendor-process gate, say that in the first email so we do not spend a week on a deal that cannot close.
Can we test the API before we talk?
Yes. Signup includes free credits against the same live endpoints production uses. Prove the routes, lookupStatus, and the { data, meta } shape first — including that infrastructure failures do not charge and requestId is present on errors. Email is useful after that — volume, invoicing, or architecture — not as a prerequisite to a first request.
Do you do custom volume pricing?
Yes. Quotes follow expected monthly volume and which endpoints dominate the mix. Pay-as-you-go credits do not expire, so unused balance is not a month-end write-off. If most of an early pack will be burned on integration, say so. For roughly 1M+ credits or invoicing, send the usage sketch and we reply with a number.
We already have clients on another vendor. Can we switch the ingestion layer only?
That is the usual enterprise path. We return public posts, comments, media metadata, and provenance fields — not a replacement listening UI. Keep your scoring, alerts, and client reports. Email the endpoints you need to remap and the monthly volume once cutover is done.
Do you version the response so a field change will not silently break us?
Schema changes are versioned, documented, and announced. You pick when to migrate. Every response includes meta.requestId so a bad hour is a ticket, not a guess. See /reliability.
What is the difference between 99.8% uptime and 98.4% request success?
99.8% is rolling 90-day API availability — whether Social Fetch answered. 98.4% is production request success — lookups that completed without an infrastructure failure. A completed not_found or private is not downtime. Neither figure is a contractual SLA unless we sign a separate agreement.
Contact
Send the sketch, get specifics.
One email with your endpoints and volume. We reply within one business day — with a number and doc references, not a discovery call.
- Direct to the team that built the API
- No forms, no ticket queue, no demo wall
support@socialfetch.dev
What to include
- Endpoints you expect to use, and whether this replaces an existing vendor
- Monthly volume once live (or a range)
- Expected concurrency and traffic shape
- Whether SOC 2 or ISO 27001 is a hard procurement gate
- Invoice and VAT needs, plus a timeline