Supplier data that never goes stale.
One API to enrich supplier records, find contacts, and pull ESG evidence. Live today. An MCP server is coming, so your own agent can call it directly.
Your supplier master is decaying.
Every procurement system holds supplier records that were accurate the day they were entered. Contacts leave. Certifications lapse. Ownership changes. Speya is the API that goes and checks: millions of suppliers searched live across 250+ sources, AI-vetted against your criteria, returned as structured records your system can write straight back into its own tables.
Three calls our customers actually make.
Enrich a supplier you already have
Pass in a supplier you already hold and get current data back. Capabilities, certifications, ownership, and status, refreshed against live sources instead of the day the record was created.
Find the contact
Named contacts at a supplier, so outreach reaches a person who still works there rather than a role inbox nobody has read in two years.
Pull ESG evidence
Certifications, compliance signals, and ESG data on a named supplier, with sources cited so your team can check the claim rather than take it on trust.
How access works.
Tell us what you are building
Send the request form below. The product, where supplier data fits in it, and the call volume you expect.
We review the fit
A short technical call. We look at your data flow and tell you honestly whether the API fits, including when it does not.
You get a sandbox key
Your first working request against real supplier data, and an engineer in the thread while you build.
Request access.
Tell us what you are building and the volume you expect. You will get a real answer, including when the API is not the right fit.
Coming soon
Speya inside your own AI agent.
Any MCP client
Microsoft Copilot, ChatGPT, Claude, or an agent your own team built. One server, whatever tool the people doing the sourcing already work in.
The same tools as the API
Search suppliers, vet them against your criteria, pull contacts and ESG evidence. Called by your agent instead of written into your code.
The API is live today
Everything the MCP server will expose is already available over the API. Request access below and start building now, rather than waiting for it.
Questions builders ask.
Who is the API for?
Two groups. Teams building procurement, PLM, or ERP products who need their users’ supplier data to stay current and are not going to build a supplier graph themselves. And internal technical procurement teams, deep research and engineering ops, who need external supplier data inside their own tooling.
Is there an MCP server?
Not yet. We are building one, so any client that speaks the Model Context Protocol can call Speya as a tool. The API covers the same ground today, so start there and you will not have to rebuild when the server lands. Tell us in the form if MCP is what you are waiting for.
Why is access gated?
Every integration is sized against real call volume, and we onboard a limited number of teams at a time so each one gets an engineer rather than a ticket queue. Tell us what you are building and you will get a straight answer quickly.
How is it priced?
API volume is priced separately from platform credits. Bring your expected monthly call volume to the review call and you will leave with a real number for your usage.
Where does the supplier data come from?
250+ sources, including registries, trade data, and the open web, searched live and AI-vetted against your criteria rather than served from a static directory.
Ready to build on it?
Tell us what you are building and the volume you expect. We review every request and onboard a limited number of teams at a time.