@ramp-kit/mcp 0.1.4 → 0.1.5

package/dist/docs.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"docs.d.ts","sourceRoot":"","sources":["../src/docs.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,eAAO,MAAM,MAAM,uGAOT,CAAC;AAEX,MAAM,MAAM,KAAK,GAAG,CAAC,OAAO,MAAM,CAAC,CAAC,MAAM,CAAC,CAAC;AAE5C,eAAO,MAAM,IAAI,EAAE,MAAM,CAAC,KAAK,EAAE,MAAM,CA0PtC,CAAC"}
+{"version":3,"file":"docs.d.ts","sourceRoot":"","sources":["../src/docs.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,eAAO,MAAM,MAAM,uGAOT,CAAC;AAEX,MAAM,MAAM,KAAK,GAAG,CAAC,OAAO,MAAM,CAAC,CAAC,MAAM,CAAC,CAAC;AAE5C,eAAO,MAAM,IAAI,EAAE,MAAM,CAAC,KAAK,EAAE,MAAM,CAgStC,CAAC"}

package/dist/docs.js

@@ -184,6 +184,44 @@ RampError { provider, code: auth | quote_expired | tx_expired |
 kyc_required | unsupported | network | provider_error }.`,
     production: `# Path to production
 
+## The integration model (how a real app ships this)
+
+A partner API key identifies the BUSINESS, not the user. One key per app,
+held server-side. End users never see or need one — they are customers
+under that partner account, identified by a customerId.
+
+browser (no key) → your backend (keys in env) → Etherfuse / Manteca
+  <RampWidget/>      @ramp-kit/server
+
+\`\`\`ts
+// backend — the only place keys exist
+createRampServer({
+  proxy:   { apiKey: process.env.ETHERFUSE_API_KEY!, environment: "production" },
+  manteca: { apiKey: process.env.MANTECA_API_KEY!,   environment: "production" },
+}).listen(8787);
+
+// frontend — EMPTY key, pointed at your backend
+new EtherfuseProvider({ apiKey: "", baseUrl: "https://api.myapp.com/ramp/etherfuse" });
+new MantecaProvider({ apiKey: "", baseUrl: "https://api.myapp.com/ramp/manteca" });
+\`\`\`
+
+Runnable reference: examples/backend-integration/ in the repo.
+
+## Dev environment setup (integrating developer)
+
+1. Keys: Etherfuse self-service (sandbox.etherfuse.com → approve own KYB →
+   api_sand… key); Manteca by request to their team. One provider is enough
+   to start — createRampServer enables whichever config it gets.
+2. .env (gitignored), read by the BACKEND — never VITE_/NEXT_PUBLIC_, which
+   would ship the key to the browser:
+   ETHERFUSE_API_KEY, ETHERFUSE_CUSTOMER_ID, MANTECA_API_KEY,
+   MANTECA_USER_ID, RAMP_ENV=sandbox|production
+3. Production: platform secret manager instead of a file.
+
+What stays the developer's job: onboarding each end user with the provider
+(KYC) to get their customerId, and resolving it from the session. The kit
+takes over from quote onward.
+
 ## Ready in code today
 - environment: "sandbox" | "production" on every provider flips base URLs;
   stellarConfigFor("production") → mainnet Horizon + passphrase.

package/dist/docs.js.map

@@ -1 +1 @@
-{"version":3,"file":"docs.js","sourceRoot":"","sources":["../src/docs.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,MAAM,CAAC,MAAM,MAAM,GAAG;IACpB,UAAU;IACV,YAAY;IACZ,eAAe;IACf,cAAc;IACd,YAAY;IACZ,iBAAiB;CACT,CAAC;AAIX,MAAM,CAAC,MAAM,IAAI,GAA0B;IACzC,QAAQ,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;gDA6BoC;IAE9C,UAAU,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;yEAkE2D;IAEvE,eAAe,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;iDA4C8B;IAE/C,YAAY,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;yDA4ByC;IAEvD,UAAU,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;kFA4BoE;IAEhF,eAAe,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;8BA2CW;CAC7B,CAAC"}
+{"version":3,"file":"docs.js","sourceRoot":"","sources":["../src/docs.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,MAAM,CAAC,MAAM,MAAM,GAAG;IACpB,UAAU;IACV,YAAY;IACZ,eAAe;IACf,cAAc;IACd,YAAY;IACZ,iBAAiB;CACT,CAAC;AAIX,MAAM,CAAC,MAAM,IAAI,GAA0B;IACzC,QAAQ,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;gDA6BoC;IAE9C,UAAU,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;yEAkE2D;IAEvE,eAAe,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;iDA4C8B;IAE/C,YAAY,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;yDA4ByC;IAEvD,UAAU,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;kFAkEoE;IAEhF,eAAe,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;8BA2CW;CAC7B,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ramp-kit/mcp",
-  "version": "0.1.4",
+  "version": "0.1.5",
   "description": "MCP server for the LATAM Ramp Kit: lets AI agents explore providers, fetch live ramp quotes, create sandbox orders, simulate PIX/SPEI deposits and inspect Stellar wallets — plus built-in documentation tools covering usage, architecture and the path to production",
   "type": "module",
   "main": "./dist/index.js",