Volume quotes
Priced on your monthly volume and endpoint mix. Mostly integration testing at first? Say so and we'll price the live run.
Enterprise
Volume pricing, SSO and procurement. No sales floor.
A stable API for public social data: posts, profiles, comments and metadata. Your product keeps the scoring and the client UI. Enterprise adds volume pricing, invoicing, single sign-on and security answers on the same live API as self-serve. No required demo.
- 99.8%
- API uptime · 90d
- 98.4%
- Request success
- ~3.2s
- Avg response
- 200
- In flight per workspace
Uptime is whether Social Fetch answered. Request success is lookups completed without an infrastructure failure. Neither is a contractual SLA. Full definitions.
Fit
Teams that already know they need a fetch layer.
Not a listening suite. You already know what you need.
Vendor switch
Replacing an incumbent
Your vendor was acquired, repriced or is sunsetting access. You need a drop-in data layer, not another analytics suite.
Embedded
Embedding data in your product
Brand protection, marketplaces, risk or social intelligence you already sell. Every plan lets you build the data into your product.
Always-on
Continuous coverage
The same brands, accounts and entities, every day, across networks. Credits don't expire, so evaluation volume isn't wasted.
Includes
Volume, security and team controls, on the same API.
Invoicing
For about 1M+ credits, or whenever procurement needs an invoice instead of a card. VAT documentation for EU buyers on request.
Security questionnaires
We answer specific data-handling questions. Zero retention stops us storing your request parameters, URLs and response previews. Practices, DPA and subprocessors are public.
SSO, directory sync and custom roles
Sign in through your identity provider (OpenID Connect), provision and remove people with SCIM 2.0, and build roles on top of Owner, Admin, Member and Billing. Included with Enterprise, or add-ons on Scale.
Team controls, built in
Invitations, two-factor authentication, per-key monthly limits, usage per teammate with CSV export, an activity log (12 months on Scale) and MCP connections scoped to the workspace. 5 seats on Growth, 25 on Scale, more by agreement. No per-seat price.
Priority support and shared Slack
Growth and Scale get priority support. Scale adds a shared Slack channel with our team, set up from Billing. Enterprise agreements add a dedicated contact.
Build on the data
White-label the data and supply it to your own customers on any plan, with no extra license. Anything beyond the standard Terms is written into your agreement.
Concurrency review
No account-wide quota on paid routes; credits are the meter. Each workspace runs up to 200 requests in flight. Need more? Email the traffic shape.
What this isn't
- Single sign-on is OpenID Connect. No SAML.
- Directory sync is SCIM 2.0 for users. No SCIM Groups.
- No account executive and no demo gate. You talk to the people who built the API.
- No SOC 2 or ISO 27001. If it's a hard gate, tell us up front.
- No contractual uptime SLA. We publish uptime instead.
Process
From first request to volume quote.
Docs first, email second, sales last.
01
Test on free credits
Same live endpoints as production. Check lookupStatus, the { data, meta } shape and requestId on errors.
02
Send the sketch
Endpoints, monthly volume, traffic shape, invoice needs. One email; we reply within a business day.
03
Get a number
A volume quote for 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.
Do you support SSO, SCIM and custom roles?
Yes. Single sign-on (OpenID Connect), directory sync (SCIM 2.0 for users) and custom roles are included with Enterprise. On Scale they're add-ons from Billing → Add-ons: $149 a month for single sign-on and directory sync, $49 for custom roles. Not supported: SAML and SCIM Groups. Tell us your identity provider and we'll confirm it fits.
What support do we get?
Every plan has email support. Growth and Scale have priority support, Scale adds a shared Slack channel with our team, and Enterprise agreements add a dedicated contact. We don't offer a contractual response-time SLA.
Can we resell or white-label the data?
Yes. Every plan lets you build the data into your product and supply it to your own customers, with no extra license. You can't resell our API itself as an API or share keys. If you need terms beyond that, we write them into your agreement.
How much concurrency can I send?
Paid routes have no request quota; credits are the meter. Each workspace can have up to 200 requests in flight; over that, requests get an uncharged 503 with Retry-After. Need more? Email the endpoint mix and traffic shape and we'll say whether it will hold.
Can you avoid storing what we query?
Yes. Zero retention stops us storing your request parameters, target URLs and response previews; we keep only minimal operational metadata such as endpoint, status, credits and request ID. Any account that has made a purchase can turn it on in Settings. Requests are still processed live by us and the data sources we use, and we won't be able to see what you fetched if you need support.
Does Social Fetch have SOC 2?
No, and we don't hold ISO 27001 either. We only fetch public social data and never take social-account passwords. Current practices are on /security, with /dpa and /subprocessors for procurement. If a certification is a hard gate, say so in your first email so neither of us wastes a week.
Can we test the API before we talk?
Yes. Signup includes free credits on the same live endpoints production uses. Check the routes, lookupStatus and the { data, meta } shape first, including that infrastructure failures aren't charged and errors carry a requestId. Email us about volume, invoicing or architecture after that, not before your first request.
Do you do custom volume pricing?
Yes. Quotes follow your monthly volume and endpoint mix. Pay-as-you-go credits don't expire, so a balance isn't a month-end write-off. If an early pack will mostly go on integration, say so. For about 1M+ credits or invoicing, send a usage sketch and we'll reply with a number.
We already have clients on another vendor. Can we switch the ingestion layer only?
That's the usual path. We return public posts, comments, media metadata and provenance fields, not a listening UI. Keep your scoring, alerts and client reports. Email the endpoints to remap and your monthly volume after cutover.
Do you version the response so a field change will not silently break us?
Yes. Schema changes are versioned, documented and announced, and you choose when to migrate. Every response carries meta.requestId, so a bad hour becomes 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 finished without an infrastructure failure. A completed not_found or private result isn't downtime. Neither is a contractual SLA.
Contact
Send the sketch, get specifics.
Email your endpoints and volume and we'll reply within a business day with a number and doc references. Prefer to talk? Book a 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'll use, and whether this replaces a vendor
- Monthly volume once live (a range is fine)
- Expected concurrency and traffic shape
- Whether SOC 2 or ISO 27001 is a hard gate
- SSO or directory sync needs, and your identity provider
- Invoice and VAT needs, and your timeline