API profile

Qredo API

Qredo API is retained only as historical custody and wallet API context. PubFi source-freshness could not fetch the Qredo developer docs or homepage, and Fusion Labs acquisition context means Discovery must not treat this as a current public Provider Profile, gateway integration, x402 route, MCP tool, or LLM-exportable source

RequestedUnavailable/deferred

Decision guide

Use it when

Reviewing historical Qredo custody and wallet API context

Check first

Planning new integrations from current provider documentation

PubFi status

Unavailable/deferred

PubFi is not claiming an active integration for this source and the public page should direct users to alternatives.

Key facts

Auth
Not listed
Pricing
Public commercial facts require product-specific review
Agent actionability
Not actionable
PubFi gateway
PubFi gateway not routeable yet
Last verified

Provider-sourced facts

Former docs evidence
Qredo developer docs were previously captured as historical API evidence, but current source-freshness fetches cannot verify those docs. Source
Corporate transition context
Fusion Labs announced acquisition of substantial Qredo assets in 2024; Discovery requires review before any current-provider claim. Source
PubFi gateway status
PubFi does not claim Qredo gateway routing, credentials, x402 payment, MCP tooling, or supplier availability.

Best fit and tradeoffs

Best for

  • Reviewing historical Qredo custody and wallet API context
  • Comparing prior Qredo evidence during migration analysis
  • They need historical context for Qredo custody and wallet API evidence.
  • They are comparing old Qredo evidence with current wallet-portfolio alternatives.
  • They need a clear noindex/export-excluded record while current machine-fetchable official docs are unavailable.

Watchouts

  • Planning new integrations from current provider documentation
  • Assuming PubFi gateway, x402, MCP, or supplier availability
  • Publishing LLM-exportable provider claims
  • Current Qredo developer docs and homepage are not machine-fetchable by PubFi source-freshness.
  • Historical docs evidence does not prove credential availability, commercial approval, uptime, or PubFi gateway runtime support.
  • Teams should use current, machine-fetchable alternatives for new integration planning until Qredo official docs are restored or replaced.

Why teams choose it

Qredo API is retained as historical custody and wallet API evidence, not as a current public Provider Profile. PubFi source-freshness cannot currently fetch the Qredo developer docs or homepage, and 2024 Fusion Labs acquisition context means the record needs transition-context review before any public claim.

Discovery keeps this record claim-safe by excluding it from public indexing and LLM export. Inclusion means PubFi preserved historical source evidence for agent-side comparison, not that PubFi has certified gateway routing, credentials, x402 payment, MCP tooling, supplier procurement, or current Qredo provider availability.

What it can cover

Qredo historical custody API evidence

Missing
Category
Wallet / portfolio
Public status
Requested
Auth requirement
API key
Access review
Not Procurable
Coverage
Multichain
Output contracts
Historical Custody Api Profile

PubFi gateway

PubFi gateway not routeable yet

This Discovery source is available for source evaluation and comparison, but PubFi does not publish a production-callable gateway route for it yet. Use this page to compare the provider, signal demand, or start a procurement/integration review instead of attempting a PubFi gateway call.

PubFi gateway call
Not published for this source
Direct gateway examples
Not available
Next step
Request integration or start supplier procurement review
  • Do not infer a PubFi gateway path from this Discovery page.
  • Use the official provider docs for direct provider integration until a PubFi readiness entry marks this source production-callable.
  • Use the Discovery request or demand-signal CTA to register integration interest with PubFi.
  • Supplier procurement, paid-plan approval, and upstream credential setup require explicit review before PubFi can route the source.

Implementation notes

Docs

High

Do not publish Qredo as a current Provider Profile while source-freshness receives unreachable responses from the developer docs and homepage.

Coverage

High

Treat Qredo evidence as historical custody/API context only; do not derive current endpoint, auth, quota, or wallet-portfolio coverage.

Schema

Medium

Require fresh official docs evidence before deriving runtime request or response contracts.

Use cases

  • Preserve historical custody API evidence for agent-side comparison

Comparison snapshot

Qredo API should be compared only as historical custody/API context. It is not ready for Discovery visibility, LLM export, or certified gateway routing until current official docs are machine-fetchable.

PubFi friction relief

Docs

Source friction
Qredo public docs were previously captured in the public documentation evidence, but source-freshness now treats the docs and homepage as unreachable.
PubFi relief
PubFi Discovery keeps historical evidence local to the agent workflow and excludes Qredo from public indexing and LLM export.

FAQ

Is Qredo API available through the PubFi gateway?

No. PubFi is not claiming Qredo gateway availability, and the Qredo profile is excluded from public indexing and LLM export until current machine-fetchable official docs are available.

Noindex status

  • editorial review is not marked reviewed
  • publication metadata is not signed off
  • publication sign-off timestamp is missing
  • publication metadata is marked noindex
  • publication metadata is not public-page ready
  • source editorial fixture review is not signed off