Integrate Indian fintech APIs faster with AI coding agents
Connect Claude Code, Cursor, Codex, Copilot, or any MCP-compatible agent to Eko Platform Services. Your agent gets the right API context, HMAC signing logic, sandbox flows, and multi-step payment and verification recipes — without digging through docs.
How to build with AI?
Three steps. You describe what you want in plain English — your AI agent finds the right API, writes the code, and tests it.
- 1
Get an AI coding agent
An AI coding agent is a tool that writes and runs code for you when you ask in plain English. Already using one? Skip to step 2. If not, choose one of these first:
Claude CodeCodexCursorAntigravityGitHub CopilotOpenCodeKiroZedAiderJetBrains AI - 2
Add EPS to your agent — one-time setup
A one-time install that teaches your agent every EPS API, correct request signing, and safe sandbox testing. The exact steps differ slightly per tool — find yours below.
Install steps for your agent - 3
Ask your agent in plain English
That’s it — describe what you need in your own words, or copy a prompt below to start:
API integrations break when agents don’t understand the real workflow
Generic API specs help with endpoints. Real fintech integrations need more: HMAC signing, access-key handling, sandbox headers, multi-step flows, OTP steps, sender/recipient state, and error-specific next actions.
Auth mistakes
HMAC signatures, timestamps, and secret-key handling are easy to get wrong.
Broken flows
Payment and banking APIs often require multiple dependent calls, not one endpoint.
Context overload
Dumping full API docs into an LLM wastes tokens and still misses the right flow.
EPS gives your agent integration-grade context
The EPS MCP server exposes only the context your agent needs at each step: endpoint discovery, request schemas, signing snippets, SDK examples, sandbox flows, and recipe-aware error handling.
Generate signed requests correctly
EPS requests are HMAC-signed with your secret-key — the exact step generic OpenAPI tooling gets wrong. Our context teaches your agent the signing scheme, so it works on the first call instead of the fifth.
Smaller context, better answers
A lazy, tiered MCP: your agent lists endpoints, then drills into just the one it needs. It never dumps the whole spec into the context window, so you keep tokens for the actual task.
Works with your coding agent
Use EPS with Claude Code, Cursor, Codex, GitHub Copilot, OpenCode, Aider, Zed, JetBrains AI, and other MCP-compatible tools.
Connect EPS to your coding agent
Install the EPS MCP server and skills into your coding agent. Claude Code and Codex have a two-step native plugin install; every other agent wires the MCP directly. Pick your tool below.
Install for your agent — Claude Code, Codex, Cursor, Copilot, Antigravity, Zed, Kiro, Aider, JetBrains…
Claude Code
/plugin marketplace add ekoindia/eps-platform/plugin install eps@ekoindiaRun both inside the Claude Code prompt. Installs the skills and the /eps command, and wires the eps MCP automatically. The manual MCP command below is only needed if you skip the plugin.
claude mcp add eps --scope project -- npx -y @ekoindia/eps-context-mcp@latest`--scope project` writes a shared `.mcp.json` committed with the repo. Use `--scope user` for every project on this machine, or drop the flag for local scope (private to this checkout, not shared).
./CLAUDE.mdEverything your agent needs
Generated from one API source of truth, so every artifact stays in lock-step with the live platform.
Local EPS MCP server
Your coding agent integrates and tests EPS APIs end-to-end on its own — discovering endpoints, wiring correct HMAC auth, and running signed sandbox calls. Zero hosting, zero secrets; the tiered context server it talks to.
npx -y @ekoindia/eps-context-mcp@latestHMAC-signed SDKs
Backend-only SDKs with HMAC signing baked in. Keep your access_key server-side.
npm i @ekoindia/eps-sdkOffline fintech API mock server
Pairs with the MCP for offline testing — replays golden sample responses with recipe-aware error branching, so your agent develops and tests without ever touching the live API.
npx -y @ekoindia/eps-mock-serverOpenAPI 3.1 spec
Canonical OpenAPI v3.1 specification of all EPS APIs in JSON format — useful for API clients, code generators, validation tools, and other OpenAPI-compatible workflows.
Postman sandbox collection
Every EPS endpoint, ready to import and run against the sandbox.
EPS context pack (fallback)
An EPS section to append to your existing AGENTS.md — for agents without MCP or skills support (Aider, JetBrains AI, …).
Real flows, not just endpoints
EPS encodes the conditional, multi-call runbooks an integration actually needs — including the error branches.
DMT (Fino) — Send Money
Full Fino DMT money-transfer flow: look up the sender, onboard them if new, add the recipient, then send an OTP-verified transfer.
- 1dmt-get-sender
Check whether the customer is already a registered DMT sender.
308 → dmt-onboard-sender · Sender not found — onboard them before continuing. - 2dmt-onboard-sender
Register a new sender when Get Sender API returns `response_type_id=308`.
- 3dmt-add-recipient
Add the beneficiary the sender wants to transfer to.
- 4dmt-send-otp
Trigger the transaction OTP sent to the sender.
- 5
AePS (Fingpay) — Cash Withdrawal
Aadhaar-enabled cash withdrawal: one-time agent activation and eKYC, daily KYC, then the biometric withdrawal.
- 1activate-aeps-fingpay
One-time activation of AePS Fingpay for the agent.
- 2aeps-fingpay-send-otp-kyc
One-time eKYC step 1 (agent onboarding, not per transaction): OTP to the agent's Aadhaar-linked mobile.
- 3aeps-fingpay-verify-otp-kyc
One-time eKYC step 2 (agent onboarding): verify the OTP with the otp_ref_id and reference_tid from step 1.
- 4aeps-fingpay-biometric-ekyc
One-time eKYC step 3 (agent onboarding): the agent's biometric PID completes eKYC.
- 5aeps-fingpay-daily-auth
Daily KYC — biometric-only, repeated once per calendar day before the agent's first transaction.
- 6
Start building with EPS in your AI coding agent
Wire EPS into your coding agent — ship your first signed EPS call today.