Eko Platform Services Logo
    AI-ready Fintech API Platform

    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.

    Install MCP ServerBrowse Toolkit
    claude
    The problem

    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.

    Why agents get it right

    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.

    Install by harness

    Connect EPS to your coding agent in one command

    Choose your tool. Copy the install command. Then ask your agent to build an EPS API flow.

    Claude Code

    MCP
    Context pack
    MCP install command
    claude mcp add eps -- npx -y @ekoindia/eps-context-mcp

    Adds to the local scope. Append `--scope project` to share via `.mcp.json`, or `--scope user` for every project.

    Context pack
    CLAUDE.md./CLAUDE.md

    Install Claude Code Plugin

    One install wires the EPS MCP, skills, and the /eps command for Claude Code.

    Enter both commands inside the Claude Code prompt, in this order:

    Step 1
    /plugin marketplace add ekoindia/eps-platform
    Step 2
    /plugin install eps@ekoindia
    The toolkit

    Everything your agent needs

    Generated from one API source of truth, so every artifact stays in lock-step with the live platform.

    Agent instruction files

    Drop-in instructions for any agent — auth, endpoints, and recipes in one file.

    AGENTS.mdCLAUDE.md.cursorrulescopilot-instructions.md

    Local EPS MCP server

    Zero hosting, zero secrets. The tiered context server your agent talks to.

    npx -y @ekoindia/eps-context-mcp

    HMAC-signed SDKs

    Backend-only SDKs with HMAC signing baked in. Keep your access_key server-side.

    npm i @ekoindia/eps-sdk
    composer require ekoindia/eps-sdk

    Offline 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-server

    OpenAPI 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.

    openapi.json

    Postman sandbox collection

    Every EPS endpoint, ready to import and run against the sandbox.

    eps.postman_collection.json
    Multi-step recipes

    Real flows, not just endpoints

    EPS encodes the conditional, multi-call runbooks an integration actually needs — including the error branches.

    DMT — Send Money

    Full domestic money transfer flow: look up the sender, onboard them if new, add the recipient, then send an OTP-verified transfer.

    1. 1
      dmt-get-sender

      Check whether the customer is already a registered DMT sender.

      463 → dmt-onboard-sender · Sender not found — onboard them before continuing.
    2. 2
      dmt-onboard-sender

      Register a new sender when Get Sender returned 463.

    3. 3
      dmt-add-recipient

      Add the beneficiary the sender wants to transfer to.

    4. 4
      dmt-send-otp

      Trigger the transaction OTP sent to the sender.

    5. 5
      dmt-initiate-transfer

      Submit the OTP-verified transfer to complete the flow.

      0 → complete

    AePS — Cash Withdrawal

    Aadhaar-enabled cash withdrawal: one-time agent activation, daily 2FA, then the biometric withdrawal.

    1. 1
      aeps-activate-fingpay

      One-time activation of AePS Fingpay for the agent.

    2. 2
      aeps-daily-auth

      Daily two-factor authentication required before transacting.

    3. 3
      aeps-cash-withdrawal

      Perform the biometric Aadhaar-enabled cash withdrawal.

      0 → complete

    Start building with EPS in your AI coding agent

    Drop the MCP into your agent and ship your first signed EPS call today.

    Install MCP Server
    npx -y @ekoindia/eps-context-mcp
    Open API DocsInstall by Harness