Start with the right scope.
Request the interfaces and technical materials relevant to your application. Access is agreed, not assumed.
Business onboarding and permitted information.
The current agent API integration scope centres on business registration and reading permitted business information. These capabilities provide an initial bridge between software and the business operating environment.
Access to onboarding or business information does not authorise moving funds, issuing cards or operating an account. Such operations require their own supported service, permission model and release approval.
An accountable authentication model.
Your integration must be associated with the correct principal and the operations approved for it. Credentials must be handled by your secure application environment, not exposed in a public website or general chat transcript.
The SUPA team supplies the authentication and environment details appropriate to the agreed interface. We also discuss how access is reviewed and withdrawn when a workflow or business relationship changes.
Tell us what you want to build.
Include the application type, the business it acts for, the information it needs and the actions you want it to perform. If you are introducing an agent, describe which decisions remain with a person.
We will identify the applicable integration scope and share the relevant reference materials. Availability is confirmed during that process; this page does not provide a self-service production API key.
Useful scope is better than assumed access.
An application that helps a business onboard needs a different set of operations from one that requests financial execution. Granting the first does not imply the second. Your team should be able to identify exactly which operations are available and which principal they serve before implementing the user journey.
During an integration discussion, we map the proposed task to the current interface and clarify the expected responses, authentication and information boundaries. If the task requires an additional service, that dependency is made explicit. This gives your engineers a concrete implementation target and lets your product team explain the actual experience to users. Broader account and payment workflows remain separate enablement decisions, not hidden capabilities unlocked by receiving credentials.
Good questions.
Clear answers.
What is the initial agent API scope?
Business registration and permitted business-information access form the current starting point. The exact enabled operations are confirmed in your integration materials.
Can I obtain a key directly from this page?
No. Access is arranged with the SUPA team after the application and scope have been established.
Can credentials be included in an agent prompt?
Credentials belong in the controlled application environment. A conversational instruction should not expose secrets or become a substitute for access controls.
A closer look.
Where could we take you?
Tell us what you want to build, connect or make possible.