PubFiDISCOVERY
Get an API key

API profile

IPFS API

IPFS API is an automation-built public Provider Profile for IPFS public API resources. Discovery has public docs evidence, but PubFi does not certify gateway runtime support for this provider

Coming soonProvider Profile
On-chain stateMultichain
Official siteMarkdownCompare sources

Decision guide

Use it when

Evaluating IPFS public API docs

Check first

Assuming PubFi gateway availability without adapter certification

PubFi status

Provider Profile

The page is an AI/Codex-processed public Provider Profile and does not claim PubFi integration, gateway access, x402 payment, or MCP tooling.

Key facts

Auth
Not listed
Pricing
Public commercial facts require product-specific review
Agent actionability
Editorial only; runtime status separate
PubFi gateway
Live Registry unavailable
Last verified

Provider-sourced facts

Public docs evidence
IPFS has public API or documentation evidence available from public sources. Source
PubFi gateway status
Automation-built Provider Profile; PubFi gateway support is not certified.

Best fit and tradeoffs

Best for

  • Evaluating IPFS public API docs
  • They want a public starting point for evaluating IPFS API documentation.
  • They need to compare IPFS against nearby crypto data providers before runtime integration work.
  • They want claim-safe evidence that can be promoted later when adapter certification exists.

Watchouts

  • Assuming PubFi gateway availability without adapter certification
  • Automation-built profiles may have incomplete category, pricing, quota, or endpoint coverage until deeper docs parsing runs.
  • Public docs evidence does not prove credential availability, commercial approval, uptime, or PubFi gateway runtime support.
  • Teams should verify endpoint shape, authentication, quotas, and terms before treating the provider as production-callable.

Why teams choose it

IPFS API is an automation-built Provider Profile based on public API corpus evidence. It helps teams inspect IPFS docs, product naming, and on chain state fit before any runtime adapter or commercial approval work begins.

Discovery keeps this page claim-safe: inclusion means public evidence was processed into a Provider Profile, not that PubFi has certified gateway routing, credentials, x402 payment, MCP tooling, or supplier procurement for IPFS.

What it can cover

IPFS API on chain state evidence

Unproven
Category
On-chain state
Public status
Requested
Auth requirement
API key
Access review
Not Procurable
Coverage
Multichain
Output contracts
Chain State Record

PubFi gateway

Live Registry unavailable

PubFi could not verify the active signed Registry generation. Checked-in Discovery content is not execution authority, so this page fails closed instead of inferring a gateway route.

Runtime status
registry_unavailable
Active capabilities
0
PubFi auth headers
Authorization: Bearer <PubFi API key> or X-PubFi-Api-Key: <PubFi API key>
Typed contract
Runtime OpenAPI
  • Retry the live Registry view or inspect the runtime OpenAPI before execution.
  • Do not infer availability from provider documentation, product copy, or repository data.

Reference details

Access

Auth methods
Not listed
Pricing model
Public commercial facts require product-specific review
Free tier
Public commercial facts require product-specific review
Starting price
Public commercial facts require product-specific review
Pricing source
Public commercial facts require product-specific review
Free rate limit
Public commercial facts require product-specific review
Paid rate limit
Public commercial facts require product-specific review

Data shape

Data types
Docs.Ipfs.Tech, Docs.Ipfs.Tech Reference, Docs.Ipfs.Tech Reference Http Api, Docs.Ipfs.Tech Reference Js Api
Protocols
REST
REST support
Yes
GraphQL support
Not listed
WebSocket support
Not listed
Streaming support
No
Webhook support
No
Feature flags
Not listed
SDKs
Not listed

Public evidence

Documentation
Provider docs
Status page
Not listed
Source coverage status
Unproven
Editorial posture
Provider Profile

Implementation notes

Docs

Medium

Review IPFS public docs and authentication requirements before any adapter certification work starts.

Coverage

Medium

Treat the current IPFS API profile as processed evidence, not as complete coverage of every chain, endpoint, or product surface.

Schema

Low

Use endpoint-specific docs evidence before deriving runtime request or response contracts.

Use cases

  • Compare IPFS API evidence before runtime integration work

Comparison snapshot

IPFS API should be compared with providers that cover similar on chain state workflows. The current automation output is enough for Discovery visibility and follow-up triage, but not for certified gateway routing.

PubFi friction relief

Docs

Source friction
IPFS public docs are available as public documentation evidence.
PubFi relief
PubFi Discovery turns the public evidence into a claim-safe Provider Profile and separates it from gateway certification.

FAQ

Is IPFS API available through the PubFi gateway?

This Provider Profile is automation-built from public evidence and does not certify PubFi gateway availability.