Setu API Setu

Name: API Setu API
Brand: API Setu
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsPayment Processingbearer, oauth2157 EndpointsREST

For Agents

Programmatically (aggregator) setup a merchant, register a beneficiary account. Covers 157 operations with bearer, oauth2 authentication.

Install Jentic One Beta

Connect the API Setu to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the API Setu, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with API Setu API.

(Aggregator) Setup a merchant

List all beneficiary accounts

Fetch a beneficiary account by id

GET STARTED

Start building with API Setu API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use API Setu API for, with concrete tasks.

★ Payments Operations

Use the API Setu to perform payments operations programmatically. The API provides 157 endpoints covering core functionality including (aggregator) setup a merchant, register a beneficiary account, list all beneficiary accounts.

Call POST /api/v1/aggregators/merchants to (aggregator) setup a merchant

Automated UPI Merchant Acquirer (UMAP) Management

Automate upi merchant acquirer (umap) operations by combining multiple API Setu endpoints. Agents can register a beneficiary account and then list all beneficiary accounts in a single workflow.

Call POST /api/v1/merchants/beneficiary-accounts to register a beneficiary account, then verify the result

AI Agent Integration via Jentic

AI agents discover and call API Setu endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer, oauth2 tokens manually.

Search Jentic for '(aggregator) setup a merchant', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

157 endpoints — comprehensive api specification for setu (setu.

METHOD

PATH

DESCRIPTION

POST

/api/v1/aggregators/merchants

(Aggregator) Setup a merchant

POST

/api/v1/merchants/beneficiary-accounts

GET

/api/v1/merchants/beneficiary-accounts

List all beneficiary accounts

GET

/api/v1/merchants/beneficiary-accounts/{id}

Fetch a beneficiary account by id

PUT

/api/v1/merchants/beneficiary-accounts/{id}/status

Update beneficiary account status

POST

/api/v1/merchants/collect

Create and invoke a collect request

GET

/api/v1/merchants/collect/{id}

Fetch collect request by id

POST

/api/v1/merchants/customer-vpas/mock/verify

Mock a customer vpa verification

POST

/api/v1/aggregators/merchants

(Aggregator) Setup a merchant

POST

/api/v1/merchants/beneficiary-accounts

GET

/api/v1/merchants/beneficiary-accounts

List all beneficiary accounts

GET

/api/v1/merchants/beneficiary-accounts/{id}

Fetch a beneficiary account by id

PUT

/api/v1/merchants/beneficiary-accounts/{id}/status

Update beneficiary account status

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your API Setu credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a collect request' or 'check a mandate status', and Jentic returns the matching API Setu operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using API Setu API through Jentic.

What authentication does the API Setu use?

The API Setu uses bearer, oauth2 authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I (aggregator) setup a merchant with the API Setu?

Yes. Use the POST /api/v1/aggregators/merchants endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the API Setu?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I (aggregator) setup a merchant through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for '(aggregator) setup a merchant'. Jentic returns the matching API Setu operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the API Setu have?

The API Setu exposes 157 endpoints covering upi merchant acquirer (umap), account aggregator, esign operations.

Can I limit what my agent is allowed to do with the API Setu?

Yes. Jentic One is self-hosted by you, so your own rules decide which API Setu operations and credentials the agent may use. Because API Setu puts mandate and account ids in the URL path, such as /api/v1/merchants/mandates/{id} and /api/v1/merchants/beneficiary-accounts/{id}, you can pin the agent to reading a specific mandate or account. You choose the operations it may call, so mandate execution or revocation stays off unless you add it.

Setu API Setu

Connect the API Setu to your agent

Capabilities

Start building with API Setu API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs