Hibachi

Hibachi is a stablecoin-native, privacy-first decentralized exchange for perpetual futures and FX trading. Built by contributors from Citadel, Tower Research, IMC, Meta, Google and Amazon, it pairs a low-latency central-limit-orderbook trading engine with a zk-verified settlement layer, so collateral only moves on-chain when validated by a zero-knowledge proof. Hibachi exposes a public REST and WebSocket API across two hosts (api.hibachi.xyz for account, trading and capital operations; data-api.hibachi.xyz for market data), an official Python SDK, a TypeScript example integration, and a CCXT integration. Authentication uses an API key in the Authorization header, and order, withdraw and transfer operations additionally require an ECDSA or HMAC request signature. It is backed by Electric Capital.

Hibachi publishes 3 APIs on the APIs.io network: Capital API, Market API, and Trade API. Tagged areas include Company, DeFi, Cryptocurrency, Exchange, and Perpetual Futures.

The Hibachi catalog on APIs.io includes 1 event-driven AsyncAPI specification.

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

🌐 Visit website 📡 Source on GitHub

38.9/100 thin ▬ flat Agent 32/100 agent ready saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0

1 APIs

Company DeFi Cryptocurrency Exchange Perpetual Futures Trading Derivatives Stablecoins WebSocket Blockchain

Kin Score

Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0

Composite quality — 38.9/100 · thin

Contract Quality 4.6 / 19

Developer Ergonomics 10.1 / 15

Access Clarity 6.7 / 15

Operational Transparency 0.3 / 10

Contract Governance 1.6 / 9

Discoverability 5.7 / 8

Regulatory Posture 6.3 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 32/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

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

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 github.com/api-evangelist/hibachi: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 3

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

Hibachi Capital API

Authenticated capital movement: balance, deposit info, withdraw, transfer

Hibachi Market API

Public market data: contracts, prices, stats, trades, klines, orderbook, funding rates

Hibachi Trade API

Authenticated trading: orders, positions, account info, settlements, leverage

Open Collections 4

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

Hibachi Capital API

OPEN COLLECTION

Hibachi Capital Market API

OPEN COLLECTION

Hibachi Capital Trade API

OPEN COLLECTION

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Hibachi WebSocket API

Hibachi exposes a WebSocket API alongside its REST API for lower-latency access to real-time trading and market data. Public market streams (/ws/market) require no API key; acco...

ASYNCAPI

Security Posture 2

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

Hibachi Authentication

apiKey/signature · 1 scheme

SECURITY

Hibachi Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Agentic Access 1

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

Hibachi Agentic Access

27 operations · 8 acting

AGENTIC

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

GettingStarted

SignUp

Sandbox

Documentation 4

Reference material describing how the API behaves

Documentation

APIReference

OpenAPI

AsyncAPI

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

AgentSkill

LLMsTxt

AgenticAccess

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conformance

ErrorCatalog

Lifecycle

Conventions

DataModel

Build 4

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

Postman

Packages

SDKs

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Commercial 3

Pricing, plans, and the legal terms of use

Pricing

Pricing

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

Overlay

Overlay

Source (apis.yml)

aid: hibachi
name: Hibachi
description: Hibachi is a stablecoin-native, privacy-first decentralized exchange for perpetual futures and FX trading. Built
  by contributors from Citadel, Tower Research, IMC, Meta, Google and Amazon, it pairs a low-latency central-limit-orderbook
  trading engine with a zk-verified settlement layer, so collateral only moves on-chain when validated by a zero-knowledge
  proof. Hibachi exposes a public REST and WebSocket API across two hosts (api.hibachi.xyz for account, trading and capital
  operations; data-api.hibachi.xyz for market data), an official Python SDK, a TypeScript example integration, and a CCXT
  integration. Authentication uses an API key in the Authorization header, and order, withdraw and transfer operations additionally
  require an ECDSA or HMAC request signature. It is backed by Electric Capital.
url: https://raw.githubusercontent.com/api-evangelist/hibachi/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- electric-capital
x-tier: enriched
x-tier-reason: portfolio-lead-enriched
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-09-03'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-19'
tags:
- Company
- DeFi
- Cryptocurrency
- Exchange
- Perpetual Futures
- Trading
- Derivatives
- Stablecoins
- WebSocket
- Blockchain
tags_raw:
- Company
- Defi
- Cryptocurrency
- Exchange
- Perpetual Futures
- Trading
- Derivatives
- Stablecoin
- WebSocket
- Blockchain
image: https://hibachi.xyz/favicon.ico
apis:
- aid: hibachi:hibachi-capital-api
  name: Hibachi Capital API
  description: 'Authenticated capital movement: balance, deposit info, withdraw, transfer'
  humanURL: https://api-doc.hibachi.xyz/
  baseURL: https://api.hibachi.xyz
  tags:
  - Capital
  properties:
  - type: OpenAPI
    url: openapi/hibachi-capital-api-openapi.yml
  - type: AsyncAPI
    url: asyncapi/hibachi-ws-asyncapi.yml
  - type: Documentation
    url: https://docs.hibachi.xyz/hibachi-docs/api-and-developer-tools.md
  - type: APIReference
    url: https://api-doc.hibachi.xyz/
  - type: Postman
    url: https://api-doc.hibachi.xyz/
- aid: hibachi:hibachi-market-api
  name: Hibachi Market API
  description: 'Public market data: contracts, prices, stats, trades, klines, orderbook, funding rates'
  humanURL: https://api-doc.hibachi.xyz/
  baseURL: https://api.hibachi.xyz
  tags:
  - Market
  properties:
  - type: OpenAPI
    url: openapi/hibachi-market-api-openapi.yml
  - type: AsyncAPI
    url: asyncapi/hibachi-ws-asyncapi.yml
  - type: Documentation
    url: https://docs.hibachi.xyz/hibachi-docs/api-and-developer-tools.md
  - type: APIReference
    url: https://api-doc.hibachi.xyz/
  - type: Postman
    url: https://api-doc.hibachi.xyz/
- aid: hibachi:hibachi-trade-api
  name: Hibachi Trade API
  description: 'Authenticated trading: orders, positions, account info, settlements, leverage'
  humanURL: https://api-doc.hibachi.xyz/
  baseURL: https://api.hibachi.xyz
  tags:
  - Trade
  properties:
  - type: OpenAPI
    url: openapi/hibachi-trade-api-openapi.yml
  - type: AsyncAPI
    url: asyncapi/hibachi-ws-asyncapi.yml
  - type: Documentation
    url: https://docs.hibachi.xyz/hibachi-docs/api-and-developer-tools.md
  - type: APIReference
    url: https://api-doc.hibachi.xyz/
  - type: Postman
    url: https://api-doc.hibachi.xyz/
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://hibachi.xyz/
- type: DeveloperPortal
  url: https://docs.hibachi.xyz/
- type: Documentation
  url: https://docs.hibachi.xyz/hibachi-docs/api-and-developer-tools.md
- type: APIReference
  url: https://api-doc.hibachi.xyz/
- type: GettingStarted
  url: https://docs.hibachi.xyz/hibachi-docs/getting-started.md
- type: Blog
  url: https://blog.hibachi.xyz/
- type: GitHubOrganization
  url: https://github.com/hibachi-xyz
- type: Pricing
  url: https://docs.hibachi.xyz/hibachi-docs/trading/fees.md
- type: SignUp
  url: https://hibachi.xyz/
- type: TermsOfService
  url: https://hibachi.xyz/terms
- type: PrivacyPolicy
  url: https://hibachi.xyz/privacy
- type: Postman
  url: https://api-doc.hibachi.xyz/
- type: OpenAPI
  url: openapi/_original/hibachi-openapi.yml
- type: AsyncAPI
  url: asyncapi/hibachi-ws-asyncapi.yml
- type: Authentication
  url: authentication/hibachi-authentication.yml
- type: Packages
  url: packages/hibachi-packages.yml
- type: SDKs
  url: packages/hibachi-packages.yml
- type: X-MCPServerCandidate
  url: mcp/hibachi-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: AgentSkill
  url: skills/_index.yml
- type: LLMsTxt
  url: llms/hibachi-llms.txt
- type: Overlay
  url: overlays/hibachi-openapi-overlay.yaml
- type: Conformance
  url: conformance/hibachi-conformance.yml
- type: ErrorCatalog
  url: errors/hibachi-problem-types.yml
- type: Lifecycle
  url: lifecycle/hibachi-lifecycle.yml
- type: Conventions
  url: conventions/hibachi-conventions.yml
- type: Sandbox
  url: sandbox/hibachi-sandbox.yml
- type: DataModel
  url: data-model/hibachi-data-model.yml
- type: AgenticAccess
  url: agentic-access/hibachi-agentic-access.yml
- type: DomainSecurity
  url: security/hibachi-domain-security.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

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/hibachi"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/hibachi/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/hibachi/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

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.

GitHub Google LinkedIn

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