Agentic bizAPIs
Send one company ID. Get the whole company back.
Until now you picked bizAPIs services one by one and wrote the sequencing, the retries and the evidence handling into your own stack. bizAPIs now runs that orchestration as agents. One request in, a complete KYB or KYC profile out, every field with its source print.
in company ID 513 097 599 · PT
out profile.json · 6 PDF prints
via API · MCP · A2A
What changes
What changes for your team
Service by service
- You contract the registry extract, the UBO lookup, the filed accounts and the tax and social security checks separately.
- Your developers decide the order, handle a portal that is down, retry, and stitch 6 responses into one record.
- Evidence lives wherever each team put it. Audits mean hunting for it.
- Every new check is a new integration project.
Agent
- You send one identifier.
- The agent runs the services in the right order, waits out a slow portal, retries, and reconciles what comes back.
- You receive one profile and one evidence pack, both structured, both traceable to the source.
- A new check is a configuration change on our side.
Flagship agent
How the KYB profile agent runs
Built from services bizAPIs clients already use in production. The example below is a company in Portugal. Typical run: under a minute, longer only when a source portal is slow.
- 01input
One input
Your onboarding flow sends a company identifier (or a personal tax ID for a KYC check). Nothing else.
- 02REGISTRY · PT
Registry
The agent pulls company status and corporate acts from the business register.
- 03UBO · PT
Beneficial owners
It resolves the UBOs in the beneficial ownership register and cross-checks names against the registry.
- 04ACCOUNTS · PT
Financials
The filed annual accounts come in: balance sheet, income statement, the numbers your scoring needs.
- 05TAX · SOCIAL · PT
Debt and standing
Tax authority and social security debt checks, signing authority, brand-to-legal-entity mapping.
- 06output
Profile plus proof
You get one structured profile and a PDF print of every source page. Ready to store, ready for the auditor.
Modes
Three ways to run agents on bizAPIs
bizAPIs agents
Ready to run. The KYB profile agent above is one of them. You call it like any other bizAPIs service and get the finished profile back.
Your agents, our tools
Every bizAPIs service is callable as a tool from your own agent framework, over MCP or agent-to-agent (A2A). Same license ID, same official sources, same zero data retention.
Custom agents
Your rules, your approval steps, your systems. We build the agent around your workflow and run it for you.
Guarantees
What does not change
An agent is a different way to call bizAPIs. The guarantees underneath are the ones you already rely on.
- Data comes from the official source, with no intermediaries.
- Every field can carry a PDF print of the page it came from.
- Nothing is retained after delivery. Credentials you pass through are never stored.
- One license ID authenticates every call, agent or not.
- ISO 27001 certified operation.
Building blocks
The use cases an agent stitches together
Each of these exists today as a service. The agent is what runs them as one job.
Questions
Questions we get
Do I have to change my current integration?
No. The services you already call keep working exactly as they do. Agents sit on top of them. Start with one flow, keep the rest.
Which protocols do your agents speak?
MCP, so any MCP-capable assistant or framework can use bizAPIs services as tools. And A2A, so your agents and ours can hand work to each other directly.
Where does the orchestration run?
On bizAPIs, inside the same ISO 27001 environment as the services. Your side receives the finished profile and the evidence pack.
Can the agent follow our own rules?
Yes. Thresholds, mandatory fields, when to stop and ask a human: that is the custom agent work we do with you.