Integration · Payments and finance
AI agents for Setu
Verify customers and businesses in India with Setu's Data and Identity APIs.
- Actions
- 7
- Read
- 5
- Write
- 2
Actions
What your agents can do in Setu
Verify customers and businesses in India with Setu's Data and Identity APIs: check a PAN with NSDL, look up a GSTIN's registration, confirm a bank account and its holder's name by a penny drop, and run Aadhaar KYC through DigiLocker (send the person a DigiLocker link, then read their Aadhaar details or fetch a document from their DigiLocker). Each product needs its own product instance ID from Setu.
Read 5
Look things up. Nothing changes.
Verify a PAN
Checks a PAN (person, company, trust, firm) with NSDL.
Verify a GSTIN
Looks up a GSTIN's registration: the business's legal and trade name, constitution (like private limited company), taxpayer type, status.
Get a DigiLocker request's status
Reads a DigiLocker request: status (unauthenticated until the person signs in, authenticated once they share, revoked) and, when authenticated, their DigiLocker ID, email and phone.
Get Aadhaar details from DigiLocker
For an authenticated DigiLocker request: the person's Aadhaar details as DigiLocker holds them, signed by UIDAI.
Fetch a document from DigiLocker
For an authenticated DigiLocker request: fetches one issued document.
Write 2
Create, change or send.
Verify a bank account
Confirms a bank account exists and is active by crediting it ₹1 (penny drop), and returns the account holder's name as the bank has it, to compare with the name you were given.
Start a DigiLocker request
Creates a DigiLocker consent request and returns its id and the url to send the person: they sign in to DigiLocker there, agree to share, and come back to your redirect_url.
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Enter the sign-in details Setu gives you for its API.
What you enter
- Client ID
- Client secret
Settings
- Environment
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your Setu data
Ask a question in plain words. The agent can verify a PAN, verify a GSTIN or get a DigiLocker request's status in Setu, then answers with what it found.
- 02
Let an agent update Setu
Have the agent verify a bank account or start a DigiLocker request in Setu as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Share what it finds in Slack
Give one agent Setu and Slack: it can verify a PAN in Setu and post a summary to a Slack channel in the same run.
FAQ
Setu and MyDeepAgents
Can MyDeepAgents connect to Setu?
Yes. The Setu connector has 7 actions: 5 read and 2 make changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Setu?
Enter the sign-in details Setu gives you for its API. You'll need: Client ID and Client secret. The connection also asks for: Environment. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in Setu without asking?
Only if you let it. Each of the 2 actions that change data can be set to wait for a person's approval before it runs.
Can I use Setu in workflows as well as agents?
Yes. Every Setu action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Setu to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.