Work with this as data
Every API 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 apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.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.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/bullet-tx-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"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.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: Bullet Trading Account Tx API
description: REST API for the Bullet exchange. Provides Binance FAPI-compatible endpoints for trading, account management, and market data.
contact:
name: Bullet
url: https://bullet.xyz
license:
name: Proprietary
version: 0.1.0
servers:
- url: /
description: Current server
- url: https://tradingapi.mainnet.bullet.xyz
description: Mainnet
- url: https://tradingapi.testnet.bullet.xyz
description: Testnet
- url: https://tradingapi.staging.bullet.xyz
description: Staging
tags:
- name: Tx
paths:
/tx/submit:
post:
summary: Submit a transaction to the rollup.
operationId: submit_tx
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/SubmitTxRequest'
required: true
responses:
'200':
description: Transaction submitted successfully
content:
application/json:
schema:
$ref: '#/components/schemas/SubmitTxResponse'
'400':
description: Invalid transaction format or validation failed
content:
application/json:
schema:
$ref: '#/components/schemas/ApiErrorResponse'
'401':
description: Invalid signature or public key
content:
application/json:
schema:
$ref: '#/components/schemas/ApiErrorResponse'
'502':
description: Upstream service unavailable
content:
application/json:
schema:
$ref: '#/components/schemas/ApiErrorResponse'
'503':
description: Validation service unavailable
content:
application/json:
schema:
$ref: '#/components/schemas/ApiErrorResponse'
tags:
- Tx
components:
schemas:
ApiErrorDetail:
oneOf:
- $ref: '#/components/schemas/JsonValidationErrorDetail'
- type: object
description: 'Typed details body. Variant order is important for untagged
deserialization: keep the more-specific shape (`JsonValidation`)
before more-permissive ones. `Upstream` holds the upstream payload
verbatim (object, string, array, number, etc.) so pre-PR clients
reading `details.error` (or `details` directly) keep working.'
TxStatus:
type: string
description: Transaction status
enum:
- unknown
- dropped
- submitted
- published
- processed
- finalized
TxResult:
type: string
description: Transaction execution result
enum:
- successful
- reverted
- skipped
ApiErrorResponse:
type: object
description: 'Structured API error response matching Bullet API format.
All error responses from the trading API conform to this schema.'
required:
- status
- message
properties:
details:
oneOf:
- type: 'null'
- $ref: '#/components/schemas/ApiErrorDetail'
description: Structured per-failure details. Shape depends on the variant.
error_id:
type:
- string
- 'null'
description: Error identifier for support.
example: 8b2e4d9f-7a1c-4f0e-9c5d-3e6a8b1c2d4f
message:
type: string
description: Human-readable error message.
example: 'Transaction validation failed: insufficient funds'
status:
type: integer
format: uint16
description: HTTP status code.
example: 400
minimum: 0
TxReceipt:
type: object
description: Transaction receipt
required:
- result
properties:
result:
$ref: '#/components/schemas/TxResult'
description: Result of transaction execution
LedgerEvent:
type: object
description: Ledger event emitted by a transaction
required:
- type
- number
- key
- value
- module
properties:
key:
type: string
description: Event key
module:
$ref: '#/components/schemas/ModuleRef'
description: Module that emitted the event
number:
type: integer
format: uint64
description: Event number
minimum: 0
tx_hash:
type: string
description: Transaction hash (if associated with a transaction)
type:
type: string
description: Event type
value:
type: object
description: Event value (arbitrary JSON)
ModuleRef:
type: object
description: Reference to a module
required:
- name
properties:
name:
type: string
description: Module name
SubmitTxResponse:
type: object
description: Response from submitting a transaction.
required:
- id
- status
properties:
events:
type: array
items:
$ref: '#/components/schemas/LedgerEvent'
description: Events emitted by the transaction
id:
type: string
description: The transaction hash
receipt:
$ref: '#/components/schemas/TxReceipt'
description: Transaction receipt (if processed)
status:
$ref: '#/components/schemas/TxStatus'
description: Transaction status
tx_number:
type: integer
format: uint64
description: Transaction number (if processed)
minimum: 0
JsonValidationErrorDetail:
type: object
description: 'One JSON shape failure: machine-readable `rule` + full serde
message including line/column. Surfaced under `details` on the wire.'
required:
- rule
- message
properties:
message:
type: string
example: 'invalid type: integer `24500000`, expected a string at line 4 column 30'
rule:
type: string
example: wrong_type
SubmitTxRequest:
type: object
required:
- body
properties:
body:
type: string
description: Base64 encoded borsh string