@ekoindia/eps-context-mcp 0.1.27 → 0.1.29

package/README.md

@@ -51,6 +51,36 @@ claude mcp add eps --transport http https://mcp.eko.in/context/mcp
 `GET https://mcp.eko.in/context/healthz` reports the bundle version it is serving.
 Rate-limited per IP at the proxy.
 
+### Non-MCP clients (REST + OpenAPI)
+
+For tools that take plain HTTP actions instead of MCP — ChatGPT custom GPTs
+(Actions), Gemini function calling, n8n, Zapier and the like — the same tools
+are served as REST, described by a generated OpenAPI 3.1 document:
+
+```
+https://mcp.eko.in/context/openapi.json
+```
+
+Every tool is `POST /context/tools/<name>` with its arguments as a JSON object
+body (empty body = no arguments). It is not a second implementation: each
+request drives the real MCP server in-process, so names, arguments and
+validation match the MCP tools exactly, and a new tool appears here
+automatically (only tools annotated `readOnlyHint: true` are published).
+
+```bash
+curl -s -X POST https://mcp.eko.in/context/tools/get_faqs \
+  -H 'content-type: application/json' -d '{"query":"billing","limit":3}'
+```
+
+- `200` → the tool's JSON result (non-JSON output such as `get_signing_snippet`
+  comes back as `{ "text": "…" }`).
+- `400` → invalid arguments or a body that is not a JSON object; `404` →
+  unknown tool, or the slug/id/recipe looked up does not exist; `503` → bundle
+  not loaded yet. Errors are `{ "error": { "code", "message" } }`.
+
+**ChatGPT custom GPT:** Configure → Actions → *Import from URL* →
+`https://mcp.eko.in/context/openapi.json`, authentication *None*.
+
 **stdio is still the better fit for CLI agents** (Claude Code, Cursor, Codex):
 it starts instantly, works offline from the baked bundle, and costs no network
 round trip per tool call.
@@ -71,6 +101,7 @@ clients can see this programmatically.
 | `get_api`             | `slug`                                                                       | Full detail for one endpoint (params, response fields, errors, examples).                                                                          |
 | `get_topic`           | `topic` (`auth` \| `errors` \| `pricing` \| `environments`)                  | One documentation topic.                                                                                                                           |
 | `get_recipe`          | `id`                                                                         | One multi-step recipe (steps + branches).                                                                                                          |
+| `get_faqs`            | `tag?`, `query?`, `limit?`                                                   | EPS FAQs (onboarding, auth, testing, integration, pricing, compliance, support). Filter by `tag`, rank by `query`. Answers are markdown with absolute links. |
 | `get_signing_snippet` | `language` (`php` \| `java` \| `csharp` \| `javascript` \| `python` \| `go`) | Paste-ready **backend** code to compute the request `secret-key`.                                                                                  |
 | `list_sdks`           | —                                                                            | The backend SDKs that wrap every endpoint: language, package, install command, minimum runtime, docs URL. Compact — no members or examples. |
 | `get_sdk`             | `language` (`javascript` \| `python` \| `php` \| `go` \| `java`; the guide slug such as `nodejs` also works) | One SDK in full: install + requirements, client config options with units, every public class/method/type, file-upload values, the error and timeout contract, and a worked `call()` example. |

package/data/eps.json

@@ -2,7 +2,7 @@
   "meta": {
     "org": "ekoindia",
     "apiVersion": "v3",
-    "bundleVersion": "cadbfb1d",
+    "bundleVersion": "01327e9c",
     "environments": [
       {
         "id": "sandbox",
@@ -13774,10 +13774,10 @@
       "name": "Vehicle & RC Verification",
       "method": "POST",
       "path": "/tools/kyc/vehicle-rc",
-      "summary": "Verify a vehicle's registration certificate (RC) in real time — owner details, chassis/engine numbers, insurance validity, blacklist status, permits, fitness, and financier info via the VAHAN national database.",
+      "summary": "Verify a vehicle's registration certificate (RC) in real time — owner details, chassis/engine numbers, insurance validity, blacklist status, permits, and financier info via the VAHAN national database.",
       "category": "verification",
       "relevance": "M",
-      "description": "Send a vehicle registration number and receive a comprehensive RC dataset in a single API call. The response covers ownership (name, father's name, address), registration details (authority, dates, expiry), insurance (company, policy number, validity), compliance (blacklist, challan, PUCC, emission norms), commercial-vehicle specifics (permit type/validity, fitness certificate, national permit, tax status), and financier information. Pan-India coverage via the VAHAN database makes it suitable for driver onboarding, fleet monitoring, motor insurance underwriting, vehicle finance, and used-car platforms. Source (VAHAN) data typically reflects real-world changes within 15–30 days.",
+      "description": "Send a vehicle registration number and receive a comprehensive RC dataset in a single API call. The response covers ownership (name, father's name, address), registration details (authority, dates, expiry), insurance (company, policy number, validity), compliance (blacklist, challan, PUCC, emission norms), commercial-vehicle specifics (permit type/validity, national permit, tax status), and financier information. Pan-India coverage via the VAHAN database makes it suitable for driver onboarding, fleet monitoring, motor insurance underwriting, vehicle finance, and used-car platforms. Source (VAHAN) data typically reflects real-world changes within 15–30 days.",
       "bestFor": "Mobility platforms, logistics companies, fleet operators, motor insurers, vehicle finance and lending platforms, used-car marketplaces.",
       "docsUrl": "https://eps.eko.in/docs/vehicle-rc",
       "headers": [
@@ -19397,5 +19397,246 @@
       ],
       "example": "import in.eko.eps.EpsClient;\nimport java.util.Map;\n\nEpsClient client = EpsClient.builder()\n    .developerKey(System.getenv(\"EPS_DEVELOPER_KEY\"))\n    .accessKey(System.getenv(\"EPS_ACCESS_KEY\"))\n    .initiatorId(\"9962981729\")\n    .environment(\"sandbox\")\n    .build();\n\nMap<String, Object> result = client.call(\"pan-lite\", Map.of(\n        \"pan_number\", \"ABCDE1234F\",\n        \"name\", \"Rajesh Kumar\",\n        \"dob\", \"1994-08-29\"\n    ));\nSystem.out.println(result);"
     }
+  ],
+  "faqs": [
+    {
+      "q": "How do I get started?",
+      "a": "Four steps: **sign up** at the [developer console page](https://eps.eko.in/console), verify your identity with PAN and address details, load your wallet to test the APIs live, then integrate and go live. Sandbox credentials are issued immediately — you can call your first endpoint before any paperwork clears.",
+      "tag": "getting-started",
+      "links": [
+        {
+          "label": "Developer docs",
+          "href": "https://eps.eko.in/docs"
+        },
+        {
+          "label": "Sign up",
+          "href": "https://eps.eko.in/console"
+        }
+      ]
+    },
+    {
+      "q": "What is EPS?",
+      "a": "**EPS (Eko Platform Services)** is the technology arm of Eko — the developer tools, AI tooling and APIs that power modern fintech integration, from money transfer and AePS to identity verification.",
+      "tag": "getting-started",
+      "links": [
+        {
+          "label": "About Eko",
+          "href": "https://eps.eko.in/about"
+        }
+      ]
+    },
+    {
+      "q": "What are the different ways to integrate with Eko EPS?",
+      "a": "Three paths, pick whichever suits your stack:\n\n- Call the **REST APIs** directly.\n- Use our official **Node.js, Python, PHP, Go or Java SDKs** to skip request-signing boilerplate.\n- Let an **AI coding agent** build it via our [MCP server and agent skills](https://eps.eko.in/ai#install).\n\nFor multi-step flows (onboard a sender, *then* transfer) start from a [transaction-flow recipe](https://eps.eko.in/recipe) rather than wiring single endpoints together yourself.",
+      "tag": "integration",
+      "links": [
+        {
+          "label": "SDK guides",
+          "href": "https://eps.eko.in/docs/sdk"
+        },
+        {
+          "label": "Developer docs",
+          "href": "https://eps.eko.in/docs"
+        },
+        {
+          "label": "Integrate with AI",
+          "href": "https://eps.eko.in/ai"
+        }
+      ]
+    },
+    {
+      "q": "How does API authentication work?",
+      "a": "Each request carries your static `developer_key` header plus a per-request `secret-key` header — an **HMAC-SHA256** signature of the current timestamp, keyed by your access key. The access key itself is **never sent over the wire**. You receive UAT keys on signup and production keys after KYC.\n\nThe [How Authentication Works](https://eps.eko.in/docs/how-auth-works) guide has the full signing recipe in five languages plus an **in-browser playground** that generates and verifies a real `secret-key` against your own access key.",
+      "tag": "auth",
+      "links": [
+        {
+          "label": "How auth works",
+          "href": "https://eps.eko.in/docs/how-auth-works"
+        },
+        {
+          "label": "Set up auth with AI",
+          "href": "https://eps.eko.in/ai#install"
+        }
+      ]
+    },
+    {
+      "q": "Is there a sandbox environment for testing?",
+      "a": "Yes. A full **sandbox** is available immediately on signup — test your integration end-to-end before going live, no commitment required. For offline work you can also run our [mock server](https://eps.eko.in/ai#artifacts) (`npx -y @ekoindia/eps-mock-server`) and get canned responses with no network calls at all.",
+      "tag": "testing",
+      "links": [
+        {
+          "label": "Get started",
+          "href": "https://eps.eko.in/docs"
+        }
+      ]
+    },
+    {
+      "q": "What are the sandbox and production base URLs?",
+      "a": "Sandbox and production share the same paths and differ **only** by base URL:\n\n- UAT / Sandbox — `https://staging.eko.in/ekoapi/v3`\n- Production — `https://api.eko.in/ekoicici/v3`\n\nA common cause of failures is calling the sandbox URL with live credentials, or vice-versa — **make sure the base URL matches the keys you are using**.",
+      "tag": "testing",
+      "links": [
+        {
+          "label": "Get started",
+          "href": "https://eps.eko.in/docs"
+        },
+        {
+          "label": "How auth works",
+          "href": "https://eps.eko.in/docs/how-auth-works"
+        }
+      ]
+    },
+    {
+      "q": "Do I need to whitelist my server IP?",
+      "a": "Production API access may require your **static public (server) IP** to be whitelisted. If your calls work from Postman but fail or time out from your own server, that is almost always the cause — share your static public IP with us so we can whitelist it.",
+      "tag": "integration",
+      "links": [
+        {
+          "label": "Developer docs",
+          "href": "https://eps.eko.in/docs"
+        }
+      ]
+    },
+    {
+      "q": "Can an AI coding agent build the integration for me?",
+      "a": "Yes — that is the fastest path. Point your agent (Claude Code, Codex, Cursor, Copilot, …) at our **MCP server** and it can look up any endpoint, generate correctly-signed requests, and scaffold the integration in your own stack. Install it in [one step from the AI hub](https://eps.eko.in/ai#install), or start from a [ready-made prompt](https://eps.eko.in/ai#quick-start).\n\nWe also publish an **OpenAPI 3.1 spec**, a **Postman collection** and per-agent **context packs** (`AGENTS.md`, `CLAUDE.md`, `.cursorrules`) so an agent has the ground truth instead of guessing.",
+      "tag": "ai",
+      "links": [
+        {
+          "label": "AI tools & MCP server",
+          "href": "https://eps.eko.in/ai"
+        },
+        {
+          "label": "Quick start prompt",
+          "href": "https://eps.eko.in/ai#quick-start"
+        }
+      ]
+    },
+    {
+      "q": "What response times can I expect?",
+      "a": "Most verification APIs return in **real time with sub-second responses**, and 99th-percentile latency stays under two seconds across verification endpoints. Transaction APIs (DMT, AePS, BBPS) respond within seconds.",
+      "tag": "integration"
+    },
+    {
+      "q": "Can the API handle high volumes?",
+      "a": "Yes. The API is designed to handle **large-scale volumes** reliably without performance degradation.",
+      "tag": "integration"
+    },
+    {
+      "q": "How is API usage billed?",
+      "a": "Usage is billed **per successful API call** with no minimum commitment. Volume-based pricing tiers are available — see the [pricing calculator](https://eps.eko.in/pricing) for indicative rates, or contact our team for a custom quote.",
+      "tag": "pricing",
+      "links": [
+        {
+          "label": "Pricing & calculator",
+          "href": "https://eps.eko.in/pricing"
+        }
+      ]
+    },
+    {
+      "q": "How are errors and failures reported?",
+      "a": "Every response carries a `status` code (`0` = success), a `response_status_id` and a human-readable `message`. **A `200 OK` with a non-zero `response_status_id` is a business failure, not a transport success** — always check both before treating a call as done. The [Status & Error Codes](https://eps.eko.in/docs/error-codes) reference lists every code and what to do about it.",
+      "tag": "integration",
+      "links": [
+        {
+          "label": "Error codes reference",
+          "href": "https://eps.eko.in/docs/error-codes"
+        }
+      ]
+    },
+    {
+      "q": "How does API versioning work?",
+      "a": "Eko APIs are versioned **in the base path** (currently `v3`). Sandbox and production share the same paths and differ only by base URL, so promoting an integration from UAT to live is a base-URL and credentials change — not a code change.",
+      "tag": "integration",
+      "links": [
+        {
+          "label": "Developer docs",
+          "href": "https://eps.eko.in/docs"
+        }
+      ]
+    },
+    {
+      "q": "How do I capture an Aadhaar fingerprint or biometric?",
+      "a": "Through a **UIDAI registered device (RDService)** — the scanner returns a signed, encrypted PID block that you pass straight through to the API. Never capture or store raw biometrics yourself.\n\nThe [Aadhaar Biometric Auth (RDService)](https://eps.eko.in/docs/aadhaar-biometric-rdservice) guide covers both the Windows/Web and Android capture paths, and includes an **in-browser device tester** — plug in your scanner and confirm it works before writing any code.",
+      "tag": "integration",
+      "links": [
+        {
+          "label": "RDService guide & device tester",
+          "href": "https://eps.eko.in/docs/aadhaar-biometric-rdservice"
+        }
+      ]
+    },
+    {
+      "q": "How do I chain multiple API calls into one flow?",
+      "a": "Most real use cases are multi-step — onboard a customer, verify them, *then* transact. Rather than stitching endpoints together from the reference, start from a [**transaction flow recipe**](https://eps.eko.in/recipe): each one is an ordered runbook showing which endpoint to call at each step and how to branch on `response_status_id`.\n\nThe same recipes are available to AI agents through our [MCP server](https://eps.eko.in/ai#install), so an agent can execute a whole flow end to end.",
+      "tag": "integration",
+      "links": [
+        {
+          "label": "Transaction flows (recipes)",
+          "href": "https://eps.eko.in/recipe"
+        }
+      ]
+    },
+    {
+      "q": "What data privacy and compliance standards does Eko follow?",
+      "a": "Eko follows applicable **RBI** and data-protection guidelines for its regulated banking and KYC services. Aadhaar-based KYC is performed **only with explicit customer consent**.",
+      "tag": "compliance"
+    },
+    {
+      "q": "How do I report an integration issue?",
+      "a": "Share the complete request and response so we can debug in one round trip:\n\n- The full `curl` (including headers)\n- The response body, verbatim\n- The timestamp of the call\n- Your `initiator_id`, `user_code` and `client_ref_id`\n\nIssues raised with these details are resolved **much** faster than \"the API is failing\".",
+      "tag": "support"
+    },
+    {
+      "q": "Are there any common integration gotchas to know?",
+      "a": "Three frequent ones:\n\n- `client_ref_id` must be **at most 20 characters** and unique per request.\n- Calling the sandbox base URL with live credentials (or vice-versa) fails auth — see [How Authentication Works](https://eps.eko.in/docs/how-auth-works).\n- The `JSESSIONID` cookie Postman adds automatically is **harmless** — it has no effect on the API and can be ignored.",
+      "tag": "integration",
+      "links": [
+        {
+          "label": "Error codes reference",
+          "href": "https://eps.eko.in/docs/error-codes"
+        }
+      ]
+    },
+    {
+      "q": "Where can I find the developer integration FAQ?",
+      "a": "Inside the API docs: [**Integration FAQs**](https://eps.eko.in/docs/faqs) collects the credential, signing, environment, error-handling and support questions in one place, right next to the endpoint reference and guides.",
+      "tag": "support",
+      "links": [
+        {
+          "label": "Integration FAQs",
+          "href": "https://eps.eko.in/docs/faqs"
+        }
+      ]
+    },
+    {
+      "q": "How does billing work?",
+      "a": "Usage is billed **per successful API call** — you pay only for verifications that return a result. There is **no monthly minimum and no lock-in**. Monthly invoices are available in the [console section](https://eps.eko.in/console) (Login to console > Manage My Account > E-Invoice / GST).",
+      "tag": "pricing"
+    },
+    {
+      "q": "Is there a setup fee?",
+      "a": "A one-time setup fee of **₹6,000 per verification API** (excl. GST) applies, plus ₹20,000 per BC/Payments API family for DMT, AePS and BBPS. It is currently **25% off** as a limited-time offer. A full waiver is also available against a higher monthly volume commitment. The [calculator](https://eps.eko.in/pricing) shows the exact one-time fee for your selection.",
+      "tag": "pricing"
+    },
+    {
+      "q": "Are the listed prices inclusive of GST?",
+      "a": "No. All listed rates are **exclusive of GST**, which is charged at 18%. The [calculator](https://eps.eko.in/pricing) lets you toggle the total between GST-inclusive and GST-exclusive views. Add your GST number in the [console section](https://eps.eko.in/console) for GST-compliant invoices (Login to console > Manage My Account > E-Invoice / GST).",
+      "tag": "pricing"
+    },
+    {
+      "q": "Am I charged for failed verifications?",
+      "a": "No. You are only billed for **successful** API responses. Failed or errored calls are not counted toward your usage — see [Status & Error Codes](https://eps.eko.in/docs/error-codes) for how success is determined.",
+      "tag": "pricing"
+    },
+    {
+      "q": "Is there a free sandbox to test the APIs?",
+      "a": "Yes. **Sandbox access is free** — sign up, test every API end-to-end with sample data, and move to production whenever you're ready. You can also run our [offline mock server](https://eps.eko.in/ai#artifacts) (`npx -y @ekoindia/eps-mock-server`) with no signup at all.",
+      "tag": "pricing"
+    },
+    {
+      "q": "Can prices change?",
+      "a": "Commercials are subject to change based on service-provider terms. Any revision is communicated in advance, and your dashboard always reflects the rates applicable to your account.",
+      "tag": "pricing"
+    }
   ]
 }

package/dist/index.js

@@ -79,6 +79,18 @@ var listSdks = (bundle) => (bundle.sdks ?? []).map((s) => ({
 var listSdkLanguages = (bundle) => (bundle.sdks ?? []).map((s) => s.lang);
 var listSdkSlugs = (bundle) => (bundle.sdks ?? []).map((s) => s.slug);
 var getSdk = (bundle, language) => (bundle.sdks ?? []).find((s) => s.lang === language || s.slug === language);
+var listFaqTags = (bundle) => [
+  ...new Set((bundle.faqs ?? []).flatMap((f) => f.tag ? [f.tag] : []))
+];
+var getFaqs = (bundle, { tag, query, limit } = {}) => {
+  const pool = (bundle.faqs ?? []).filter((f) => !tag || f.tag === tag);
+  const terms = (query ?? "").toLowerCase().split(/\s+/).filter(Boolean);
+  const ranked = terms.length ? pool.map((f) => {
+    const hay = `${f.q} ${f.a}`.toLowerCase();
+    return { f, score: terms.filter((t) => hay.includes(t)).length };
+  }).filter((s) => s.score > 0).sort((x, y) => y.score - x.score).map((s) => s.f) : pool;
+  return limit !== void 0 ? ranked.slice(0, limit) : ranked;
+};
 
 // src/auth-debug.ts
 var MS_DIGITS = 13;
@@ -319,7 +331,8 @@ var json = (value) => ({
 });
 var notFound = (message) => ({
   isError: true,
-  content: [{ type: "text", text: message }]
+  content: [{ type: "text", text: message }],
+  _meta: { httpStatus: 404 }
 });
 var READ_ONLY = {
   readOnlyHint: true,
@@ -440,6 +453,22 @@ var createEpsServer = (bundle, source, versionState) => {
       );
     }
   );
+  const faqTags = listFaqTags(bundle);
+  const faqTagSchema = faqTags.length ? z.enum(faqTags) : z.string();
+  server.registerTool(
+    "get_faqs",
+    {
+      title: "Get FAQs",
+      description: "EPS FAQs (onboarding, auth, testing, integration, pricing, compliance, support). Answers are markdown with absolute links. Filter by tag and/or rank by query; with neither, all FAQs are returned.",
+      inputSchema: {
+        tag: faqTagSchema.optional().describe(`One of: ${faqTags.join(", ")}`),
+        query: z.string().optional().describe("Free-text question to rank by"),
+        limit: limitSchema.describe("Max FAQs to return (default: all)")
+      },
+      annotations: READ_ONLY
+    },
+    async ({ tag, query, limit }) => json(getFaqs(bundle, { tag, query, limit }))
+  );
   server.registerTool(
     "get_signing_snippet",
     {

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@ekoindia/eps-context-mcp",
-	"version": "0.1.27",
+	"version": "0.1.29",
 	"description": "Local MCP server giving AI coding agents context for Eko Platform Services (EPS) APIs.",
 	"license": "MIT",
 	"type": "module",