ZebPay website screenshot

ZebPay

ZebPay is an Indian cryptocurrency exchange offering spot trading in INR and USDT pairs and crypto futures. It publishes REST APIs for spot (sapi.zebpay.com, documented on GitHub), a legacy spot API (www.zebapi.com) and futures (futuresbe.zebpay.com), public Postman documentation at docs.zebpay.com and apidocs.zebpay.com, WebSocket market streams, futures webhooks, and an MCP server for AI-assisted trading.

ZebPay publishes 9 API contracts indexed on the APIs.io network, including Futures API, Futures > Exchange API, Futures > Market API, and 6 more. Tagged areas include Company, Cryptocurrency, Exchange, Trading, and Futures.

The ZebPay catalog on APIs.io includes 1 Spectral governance ruleset.

ZebPay’s developer surface includes authentication, documentation, API reference, getting-started guide, engineering blog, pricing, signup flow, and 18 more developer resources.

34.9/100 thin ▼ -7.5 Agent 46/100 agent ready Heartbeat 100/100 alive Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →
2 published contracts 1 MCP Servers
CompanyCryptocurrencyExchangeTradingFuturesIndiaMarket DataMCP

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0
Regulatory Posture applies to this provider. Its tags matched the Securities & Market Data regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.
The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site. Kin Score badge preview for ZebPay It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/zebpay/"><img src="https://apis.io/badge/zebpay/card.svg" alt="ZebPay on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
  • Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
  • Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
  • A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
  • Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
  • Typed Event Surface +6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks
  • Agent Skills +5 pts — skills artifact present, graded by who authored it
4 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/zebpay/apis.yml: open an issue on github.com/api-evangelist/zebpay to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 3

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

measured — observed by APIs.io (documented)
measured — observed by APIs.io (verified)
measured — observed by APIs.io (published)

APIs 9

Individual APIs this provider publishes, each with its own machine-readable definition.

ZebPay Spot API v2

Spot trading API on sapi.zebpay.com (market data, orders, balances), documented in markdown in the zebpay-api-references GitHub repository. No machine-readable contract is publi...

ZebPay Futures API

The Futures API from ZebPay — 1 operation(s) for futures.

ZebPay Futures > Exchange API

The Futures > Exchange API from ZebPay — 2 operation(s) for futures > exchange.

ZebPay Futures > Market API

The Futures > Market API from ZebPay — 5 operation(s) for futures > market.

ZebPay Futures > Trade API

The Futures > Trade API from ZebPay — 9 operation(s) for futures > trade.

ZebPay Futures > User Leverage API

The Futures > User Leverage API from ZebPay — 2 operation(s) for futures > user leverage.

ZebPay Futures > Wallet API

The Futures > Wallet API from ZebPay — 1 operation(s) for futures > wallet.

ZebPay Market API

These APIs returns market details including ticker(s), book (pending orders), trades (executed orders) etc.

ZebPay Trade API

This endpoint allows users to read order data, create a new order, or cancel a previously placed order. Signature Generation for POST Meth

Scroll for all 9

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

ZebPay MCP Server

ZebPay publishes an MCP server in its own GitHub organization (github.com/zebpay/zebpay-mcp-server, TypeScript, @modelcontextprotocol/sdk) exposing spot and futures market-data ...

MCP SERVER

ZebPay API pricing

Rate limits

Rate-limit details →

Rate Limits 1

Documented rate limits and quota policies.

Zebpay Rate Limits

3 limits

RATE LIMITS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

ZebPay

SLA

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

ZebPay API Rules

11 rules · 9 errors 1 warnings 1 info

SPECTRAL

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Zebpay Authentication

http · 1 scheme

SECURITY

Zebpay Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Zebpay Agentic Access

34 operations · 8 acting

34 operations · 8 acting

AGENTIC

Resources

Get Started 2

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Build 4

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Operate 2

Status, limits, changes, and where to get help

Commercial 1

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Other 2

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: zebpay
name: ZebPay
description: ZebPay is an Indian cryptocurrency exchange offering spot trading in INR and USDT pairs and crypto futures. It
  publishes REST APIs for spot (sapi.zebpay.com, documented on GitHub), a legacy spot API (www.zebapi.com) and futures (futuresbe.zebpay.com),
  public Postman documentation at docs.zebpay.com and apidocs.zebpay.com, WebSocket market streams, futures webhooks, and
  an MCP server for AI-assisted trading.
url: https://raw.githubusercontent.com/api-evangelist/zebpay/refs/heads/main/apis.yml
x-type: company
x-source: harvest:market-gap:crypto-exchanges
x-tier: profiled
x-tier-reason: enriched
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - rate-limits
  - security
  generated: '2026-11-06'
  method: derived
specificationVersion: '0.20'
created: '2026-10-13'
modified: '2026-10-13'
tags:
- Company
- Cryptocurrency
- Exchange
- Trading
- Futures
- India
- Market Data
- MCP
tags_raw:
- Company
- Cryptocurrency
- Exchanges
- Trading
- Futures
- India
- Market Data
- MCP
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: RateLimits
  url: rate-limits/zebpay-rate-limits.yml
- type: AgenticAccess
  url: agentic-access/zebpay-agentic-access.yml
- type: Spectral
  url: rules/zebpay-rules.yml
- type: Vocabulary
  url: vocabulary/zebpay-vocabulary.yml
- type: Conformance
  url: conformance/zebpay-conformance.yml
- type: LLMsTxt
  url: llms/zebpay-llms.txt
- type: MCPServer
  url: mcp/zebpay-mcp.yml
- type: WellKnown
  url: well-known/zebpay-well-known.yml
- type: Hosts
  url: hosts/zebpay-hosts.yml
- type: Vendors
  url: vendors/zebpay-vendors.yml
- type: SDKs
  url: packages/zebpay-packages.yml
- type: Packages
  url: packages/zebpay-packages.yml
- type: Security
  url: https://zebpay.com/features/security
- type: Authentication
  url: authentication/zebpay-authentication.yml
- type: DomainSecurity
  url: security/zebpay-domain-security.yml
- type: Website
  url: https://zebpay.com
- type: Documentation
  url: https://docs.zebpay.com/
- type: APIReference
  url: https://apidocs.zebpay.com/
- type: GettingStarted
  url: https://zebpay.com/app/api-trading
- type: Blog
  url: https://zebpay.com/blog
- type: Pricing
  url: https://zebpay.com/features/pricing
- type: SignUp
  url: https://onboarding.zebpay.com/onboarding
- type: Support
  url: https://help.zebpay.com/support/home
- type: GitHubOrganization
  url: https://github.com/zebpay
- type: Postman
  url: https://docs.zebpay.com/
apis:
- aid: zebpay:zebpay-spot-api
  name: ZebPay Spot API v2
  description: Spot trading API on sapi.zebpay.com (market data, orders, balances), documented in markdown in the zebpay-api-references
    GitHub repository. No machine-readable contract is published for it.
  humanURL: https://github.com/zebpay/zebpay-api-references/tree/main/spot/api-reference
  baseURL: https://sapi.zebpay.com
  tags:
  - Cryptocurrency
  - Trading
  - Spot
  properties:
  - type: Documentation
    url: https://github.com/zebpay/zebpay-api-references/blob/main/spot/api-reference/README.md
- aid: zebpay:zebpay-futures-api
  name: ZebPay Futures API
  description: The Futures API from ZebPay — 1 operation(s) for futures.
  humanURL: https://apidocs.zebpay.com/
  baseURL: https://futuresbe.zebpay.com
  tags:
  - Futures
  properties:
  - type: OpenAPI
    url: openapi/zebpay-futures-api-openapi.yml
  - type: PostmanCollection
    url: postman/zebpay-api-collection.json
  - type: Documentation
    url: https://apidocs.zebpay.com/
- aid: zebpay:zebpay-futures-exchange-api
  name: ZebPay Futures > Exchange API
  description: The Futures > Exchange API from ZebPay — 2 operation(s) for futures > exchange.
  humanURL: https://apidocs.zebpay.com/
  baseURL: https://futuresbe.zebpay.com
  tags:
  - Futures > Exchange
  properties:
  - type: OpenAPI
    url: openapi/zebpay-futures-exchange-api-openapi.yml
  - type: PostmanCollection
    url: postman/zebpay-api-collection.json
  - type: Documentation
    url: https://apidocs.zebpay.com/
- aid: zebpay:zebpay-futures-market-api
  name: ZebPay Futures > Market API
  description: The Futures > Market API from ZebPay — 5 operation(s) for futures > market.
  humanURL: https://apidocs.zebpay.com/
  baseURL: https://futuresbe.zebpay.com
  tags:
  - Futures > Market
  properties:
  - type: OpenAPI
    url: openapi/zebpay-futures-market-api-openapi.yml
  - type: PostmanCollection
    url: postman/zebpay-api-collection.json
  - type: Documentation
    url: https://apidocs.zebpay.com/
- aid: zebpay:zebpay-futures-trade-api
  name: ZebPay Futures > Trade API
  description: The Futures > Trade API from ZebPay — 9 operation(s) for futures > trade.
  humanURL: https://apidocs.zebpay.com/
  baseURL: https://futuresbe.zebpay.com
  tags:
  - Futures > Trade
  properties:
  - type: OpenAPI
    url: openapi/zebpay-futures-trade-api-openapi.yml
  - type: PostmanCollection
    url: postman/zebpay-api-collection.json
  - type: Documentation
    url: https://apidocs.zebpay.com/
- aid: zebpay:zebpay-futures-user-leverage-api
  name: ZebPay Futures > User Leverage API
  description: The Futures > User Leverage API from ZebPay — 2 operation(s) for futures > user leverage.
  humanURL: https://apidocs.zebpay.com/
  baseURL: https://futuresbe.zebpay.com
  tags:
  - Futures > User Leverage
  properties:
  - type: OpenAPI
    url: openapi/zebpay-futures-user-leverage-api-openapi.yml
  - type: PostmanCollection
    url: postman/zebpay-api-collection.json
  - type: Documentation
    url: https://apidocs.zebpay.com/
- aid: zebpay:zebpay-futures-wallet-api
  name: ZebPay Futures > Wallet API
  description: The Futures > Wallet API from ZebPay — 1 operation(s) for futures > wallet.
  humanURL: https://apidocs.zebpay.com/
  baseURL: https://futuresbe.zebpay.com
  tags:
  - Futures > Wallet
  properties:
  - type: OpenAPI
    url: openapi/zebpay-futures-wallet-api-openapi.yml
  - type: PostmanCollection
    url: postman/zebpay-api-collection.json
  - type: Documentation
    url: https://apidocs.zebpay.com/
- aid: zebpay:zebpay-market-api
  name: ZebPay Market API
  description: <p>These APIs returns market details including ticker(s), book (pending orders), trades (executed orders) etc.</p>
  humanURL: https://apidocs.zebpay.com/
  baseURL: https://futuresbe.zebpay.com
  tags:
  - Markets
  tags_raw:
  - Market
  properties:
  - type: OpenAPI
    url: openapi/zebpay-market-api-openapi.yml
  - type: PostmanCollection
    url: postman/zebpay-api-collection.json
  - type: Documentation
    url: https://apidocs.zebpay.com/
- aid: zebpay:zebpay-trade-api-api
  name: ZebPay Trade API
  description: "<p>This endpoint allows users to read order data, create a new order, or cancel a previously placed order.</p>\n\
    <h3 id=\"signature-generation-for-post-methods\"><strong>Signature Generation for POST Methods:</strong></h3>\n<p>The\
    \ following JavaScript code should be added to the <strong>Pre-request Script</strong> tab in Postman. It automatically\
    \ generates the required signature and includes the API key and signature in the request headers.</p>\n<pre class=\"click-to-expand-wrapper\
    \ is-snippet-wrapper\"><code class=\"language-javascript\">// Import crypto for HMAC-SHA256 signature calculation\nconst\
    \ CryptoJS = require('crypto-js');\n// API key and secret\nconst APIKEY = '';\nconst SECRET = '';\n// Generate the current\
    \ timestamp\nconst timestamp = Date.now(); // Unix time in milliseconds\n//read boday data and pass update timestamp\n\
    const body = pm.request.body.raw\nconst payload = JSON.parse(body);\npayload.timestamp = timestamp;\n// Stringify the\
    \ payload\nconst payloadString = JSON.stringify(payload);\n// Function to calculate HMAC-SHA256 signature\nfunction calculateSignature(payload,\
    \ secret) {\n    const hash = CryptoJS.HmacSHA256(payload, secret);\n    return hash.toString(CryptoJS.enc.Hex);\n}\n\
    // Calculate the signature\nconst signature = calculateSignature(payloadString, SECRET);\n// Set headers dynamically\n\
    pm.request.headers.upsert({\n    key: \"X-AUTH-APIKEY\",\n    value: APIKEY,\n});\npm.request.headers.upsert({\n    key:\
    \ \"X-AUTH-SIGNATURE\",\n    value: signature,\n});\n// Replace request body with the dynamically generated payload\n\
    pm.request.body.update(payloadString);\n\n</code></pre>\n<h3 id=\"signature-generation-for-get-methods\"><strong>Signature\
    \ Generation for GET Methods:</strong></h3>\n<pre class=\"click-to-expand-wrapper is-snippet-wrapper\"><code class=\"\
    language-javascript\">// Import crypto for HMAC-SHA256 signature calculation\nconst CryptoJS = require('crypto-js');\n\
    // API key and secret\nconst APIKEY = '';\nconst SECRET = '';\n// Function to calculate HMAC-SHA256 signature\nfunction\
    \ calculateSignature(payload, secret) {\n    const hash = CryptoJS.HmacSHA256(payload, secret); // Use CryptoJS for HMAC\n\
    \    return hash.toString(CryptoJS.enc.Hex); // Convert to hexadecimal\n}\n// Generate a timestamp\nconst timestamp =\
    \ Date.now(); // Current Unix timestamp in milliseconds\n// Access the query parameters from the request URL\nlet queryParams\
    \ = pm.request.url.query;\n// Convert query parameters into a key-value object\nlet queryObject = {};\nqueryParams.each(param\
    \ =&gt; {\n    queryObject[param.key] = param.value;\n});\n// Update or set the parameter dynamically\nqueryObject['timestamp']\
    \ = Date.now() // Update 'timestamp' parameter\n// Convert query parameters to query string\nconst queryString = Object.entries(queryObject)\n\
    \    .map(([key, value]) =&gt; `${encodeURIComponent(key)}=${encodeURIComponent(value)}`)\n    .join('&amp;');\n// Generate\
    \ the signature\nconst signature = calculateSignature(queryString, SECRET);\n// Set headers dynamically\npm.request.headers.upsert({\n\
    \    key: \"X-AUTH-APIKEY\",\n    value: APIKEY,\n});\npm.request.headers.upsert({\n    key: \"X-AUTH-SIGNATURE\",\n \
    \   value: signature,\n});\n// Update the URL with the query parameters\npm.request.url.query.clear(); // Clear existing\
    \ query params\nqueryString.split('&amp;').forEach((param) =&gt; {\n    const [key, value] = param.split('=');\n    pm.request.url.query.add({\
    \ key, value });\n});\n\n</code></pre>"
  humanURL: https://apidocs.zebpay.com/
  baseURL: https://futuresbe.zebpay.com
  tags:
  - Trade API
  properties:
  - type: OpenAPI
    url: openapi/zebpay-trade-api-api-openapi.yml
  - type: PostmanCollection
    url: postman/zebpay-api-collection.json
  - type: Documentation
    url: https://apidocs.zebpay.com/
x-enrichment:
  date: '2026-10-13'
  status: enriched
  artifacts_added: 14
  pass: local-v5

ZebPay API — frequently asked questions

Does ZebPay have an API?

Yes. APIs.io lists 9 APIs from ZebPay, including ZebPay Spot API v2, ZebPay Futures API and ZebPay Futures > Exchange API, and 6 more.

Is there an OpenAPI specification for the ZebPay API?

Yes. APIs.io indexes 8 OpenAPI specifications for ZebPay, each linked for download from this page.

How do I authenticate with the ZebPay API?

ZebPay documents its authentication (http · 1 scheme). The details are profiled on APIs.io as Zebpay Authentication.

Does ZebPay have an MCP server?

Yes. APIs.io lists 1 MCP server for ZebPay: ZebPay publishes an MCP server in its own GitHub organization (github.com/zebpay/zebpay-mcp-server, TypeScript, @modelcontextprotocol/sdk) exposing spot and futures market-data and trading tools over

Is the ZebPay API ready for AI agents?

ZebPay has a Kin Score of 34.9 out of 100 (thin) and an Agent Readiness score of 45.6 (agent-ready), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/zebpay"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/zebpay/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/zebpay/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.