Arkham Tx API

The Tx API from Arkham — 1 operation(s) for tx.

Operations 2

GET /tx/{hash} Get transaction details #
POST /tx Get Arkham transaction details #

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.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/arkham:arkham-tx-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

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.

OpenAPI Specification

arkham-tx-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Arkham Tx API
  x-refined-note:
  - x-guidance differs across the merged source definitions and was not carried
  version: '1.0'
  description: 'Operations tagged Tx across 2 of this provider''s published API definitions: arkham-openapi-original.json, arkham-openapi.json. Each path carries the servers of the definition it was published in.'
servers:
- url: https://api.arkm.com/x402
tags:
- name: Tx
paths:
  /tx/{hash}:
    get:
      summary: Get transaction details
      description: 'Retrieves detailed information about a specific blockchain transaction using its hash.


        The endpoint searches across all supported chains to find the transaction. If it is not found in confirmed transactions, it also checks the mempool for pending transactions.


        **Response shape.** The response body is a JSON object keyed by chain identifier (for example "ethereum"). Because the same hash format can appear on more than one chain, the object may contain more than one entry, one per chain on which the transaction was found. Each value holds that chain''s transaction details. The exact set of fields varies by chain, but consumers can generally expect:


        - the block number and block timestamp the transaction was included in,

        - the sender and recipient addresses,

        - gas used and gas-related fields, along with the transaction fee,

        - the value transferred in native units and its USD value at the time,

        - token details for any tokens involved in the transfer.


        **Not found.** If the hash is not found on any supported chain (neither confirmed nor pending), the endpoint returns 404.'
      operationId: GetTransaction
      parameters:
      - name: hash
        in: path
        description: The transaction hash to look up.
        required: true
        schema:
          type: string
          description: The transaction hash to look up.
          example: '0x5c504ed432cb51138bcf09aa5e8a410dd4a1e204ef84bfed1be16dfba1b22060'
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                type: object
                additionalProperties:
                  $ref: '#/components/schemas/TxInfo'
                example: {}
        '400':
          description: Bad Request
        '500':
          description: Internal Server Error
      tags:
      - Tx
  /tx:
    post:
      operationId: tx
      summary: Get Arkham transaction details
      tags:
      - Tx
      x-payment-info:
        price:
          mode: fixed
          currency: USD
          amount: '0.40'
        protocols:
        - x402: {}
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                hash:
                  anyOf:
                  - type: string
                  - type: number
                  - type: boolean
                  - type: array
                    items:
                      anyOf:
                      - type: string
                      - type: number
                      - type: boolean
                  description: The transaction hash to look up.
              required:
              - hash
              additionalProperties:
                anyOf:
                - type: string
                - type: number
                - type: boolean
                - type: array
                  items:
                    anyOf:
                    - type: string
                    - type: number
                    - type: boolean
            example:
              hash: '0x5c504ed432cb51138bcf09aa5e8a410dd4a1e204ef84bfed1be16dfba1b22060'
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema: {}
        '400':
          $ref: '#/components/responses/BadRequest400'
        '402':
          $ref: '#/components/responses/PaymentRequired402'
        '404':
          $ref: '#/components/responses/NotFound404'
        '429':
          $ref: '#/components/responses/RateLimited429'
        5XX:
          $ref: '#/components/responses/UpstreamError5xx'
      security: []
      description: Get Arkham transaction details. $0.40 per call.
    servers:
    - url: https://api.arkm.com/x402
components:
  schemas:
    TxInfo: {}
  responses:
    PaymentRequired402:
      description: 'Payment challenge, not an application error. Read the base64 x402 v2 challenge from PAYMENT-REQUIRED, sign it, and retry the same request with PAYMENT-SIGNATURE. If a post-payment 402 omits PAYMENT-REQUIRED, verification failed: read the new challenge, re-sign, and retry once.'
      headers:
        PAYMENT-REQUIRED:
          description: Base64-encoded x402 v2 payment requirements. Its accepts array contains the scheme, network, asset, atomic amount, and payTo address.
          schema:
            type: string
    NotFound404:
      description: The upstream Arkham resource does not exist. Fatal for the same input. Payment is not settled.
    UpstreamError5xx:
      description: Arkham failed or timed out, including 502 and 504 responses. Retry with backoff. x402 payments and MPP transaction credentials are not settled for failed requests; MPP hash credits are redeemed at admission and are not refunded automatically.
    RateLimited429:
      description: Per-wallet endpoint rate limit exceeded. Retry with at least 1 second of backoff; keep heavy endpoints at no more than 5 requests per second.
    BadRequest400:
      description: 'Fatal for the request as written: validation failed or required JSON body fields are missing. Fix the request; do not retry it unchanged. Payment is not settled.'
      content:
        application/json:
          schema:
            type: object
            required:
            - success
            - error
            properties:
              success:
                type: boolean
                enum:
                - false
              error:
                type: string
              issues:
                type: array
                description: Per-field validation issues, present when schema validation produced them.
  securitySchemes:
    siwx:
      type: apiKey
      in: header
      name: SIGN-IN-WITH-X
x-refined-from:
- arkham-openapi-original.json
- arkham-openapi.json