IPFS

IPFS Multibase API

The Multibase API from IPFS — 4 operation(s) for multibase.

Documentation GitHub OpenAPI

Operations 4

POST /api/v0/multibase/decode #

POST /api/v0/multibase/encode #

POST /api/v0/multibase/list #

POST /api/v0/multibase/transcode #

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

GitHub Google LinkedIn

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

OpenAPI Specification

openapi: 3.2.0
info:
  title: IPFS RPC Multibase API
  version: v0
  description: 'When a Kubo IPFS node is running as a daemon, it exposes an HTTP RPC API that allows you to control the node and run the same commands you can from the command line.


    In many cases, using this RPC API is preferable to embedding IPFS directly in your program — it allows you to maintain peer connections that are longer lived than your app and you can keep a single IPFS node running instead of several if your app can be launched multiple times. In fact, the `ipfs` CLI commands use this RPC API when operating in online mode.'
  x-providerName: IPFS
  x-logo:
    url: https://raw.githubusercontent.com/ipfs/ipfs-docs/55fe8bc6a53ba3b9023951fb4b432efbbc81fba5/docs/.vuepress/public/images/ipfs-logo.svg
servers:
- description: Local IPFS node
  url: http://localhost:5001
- description: Local IPFS node
  url: http://127.0.0.1:5001
- description: Infura hosted IPFS node
  url: https://ipfs.infura.io:5001
tags:
- name: Multibase
paths:
  /api/v0/multibase/decode:
    post:
      operationId: multibase/decode
      description: Decode multibase string
      externalDocs:
        url: https://docs.ipfs.tech/reference/kubo/rpc/#api-v0-multibase-decode
      parameters: []
      requestBody:
        description: Argument `encoded_file` is of file type. This endpoint expects one or several files (depending on the command) in the body of the request as 'multipart/form-data'.
        content: {}
      responses:
        '200':
          description: Successful response
      tags:
      - Multibase
  /api/v0/multibase/encode:
    post:
      operationId: multibase/encode
      description: Encode data into multibase string
      externalDocs:
        url: https://docs.ipfs.tech/reference/kubo/rpc/#api-v0-multibase-encode
      parameters:
      - name: b
        in: query
        description: multibase encoding.
        schema:
          type: string
          default: base64url
      requestBody:
        description: Argument `file` is of file type. This endpoint expects one or several files (depending on the command) in the body of the request as 'multipart/form-data'.
        content: {}
      responses:
        '200':
          description: Successful response
      tags:
      - Multibase
  /api/v0/multibase/list:
    post:
      operationId: multibase/list
      description: List available multibase encodings.
      externalDocs:
        url: https://docs.ipfs.tech/reference/kubo/rpc/#api-v0-multibase-list
      parameters:
      - name: prefix
        in: query
        description: also include the single letter prefixes in addition to the code.
        schema:
          type: boolean
      - name: numeric
        in: query
        description: also include numeric codes.
        schema:
          type: boolean
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              example:
              - Code: <int>
                Name: <string>
      tags:
      - Multibase
  /api/v0/multibase/transcode:
    post:
      operationId: multibase/transcode
      description: Transcode multibase string between bases
      externalDocs:
        url: https://docs.ipfs.tech/reference/kubo/rpc/#api-v0-multibase-transcode
      parameters:
      - name: b
        in: query
        description: multibase encoding.
        schema:
          type: string
          default: base64url
      requestBody:
        description: Argument `encoded_file` is of file type. This endpoint expects one or several files (depending on the command) in the body of the request as 'multipart/form-data'.
        content: {}
      responses:
        '200':
          description: Successful response
      tags:
      - Multibase
externalDocs:
  url: https://docs.ipfs.tech/reference/kubo/rpc/