API profile

Request Network API

Request Network API is preserved in Discovery as a payment and invoicing API comparison profile. Official docs describe creating requests, payment calldata, payouts, crypto-to-fiat flows, compliance, and webhooks. PubFi does not certify this provider as a crypto data source, gateway route, x402 supplier, MCP tool, or runtime integration

Coming soonNeeds re-verification

Decision guide

Use it when

Evaluating Request Network payment and invoicing API docs

Check first

Assuming Request is a high-confidence crypto data source or PubFi gateway integration

PubFi status

Needs re-verification

The editorial profile remains useful, but its public evidence is degraded. Reverify upstream docs and commercial terms; use the live Registry and runtime OpenAPI for PubFi execution decisions.

Key facts

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

Provider-sourced facts

Public docs evidence
Request Network API official docs describe payment requests, payment calldata, payouts, crypto-to-fiat, compliance, and webhooks. Source
PubFi gateway status
Guarded payment API profile; PubFi gateway, x402, MCP, supplier, and runtime support are not certified.

Best fit and tradeoffs

Best for

  • Evaluating Request Network payment and invoicing API docs
  • They want a public starting point for evaluating Request Network payment and invoicing API documentation.
  • They need to compare payment-workflow APIs against data-source providers before runtime integration work.
  • They want claim-safe evidence that keeps payment API availability separate from PubFi data-source certification.

Watchouts

  • Assuming Request is a high-confidence crypto data source or PubFi gateway integration
  • The Request Network API evidence is payment-workflow oriented, so it must not be promoted as ordinary crypto market data or on-chain analytics coverage.
  • Public docs evidence does not prove credential availability, compliance approval, pricing, uptime, or PubFi gateway runtime support.
  • Teams should verify endpoint shape, authentication, quotas, compliance requirements, and terms before treating the provider as production-callable.

Why teams choose it

Request Network API is a guarded payment and invoicing API profile, not a high-confidence crypto data-source recommendation. Current official evidence describes creating payment requests, payment calldata, payouts, crypto-to-fiat flows, compliance, supported chains/currencies, and payment webhooks.

Discovery keeps this page claim-safe for evaluation and comparison only: inclusion means public Request Network API evidence was processed into a profile, not that PubFi has certified data-source routing, gateway credentials, x402 payment, MCP tooling, supplier procurement, or runtime support for Request.

What it can cover

Request Network API payment workflow evidence

Degraded
Category
On-chain state
Public status
Requested
Auth requirement
API key
Access review
Not Procurable
Coverage
Multichain
Output contracts
Payment Workflow Profile

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.

Implementation notes

Gotcha

High

Keep Request Network API out of high-confidence data-source routing; LLM export is only safe with evaluation/comparison wording.

Docs

Medium

Use the Request Network API reference and llms-full docs mirror for current endpoint evidence; older GitBook subpage URLs can return HTTP 404 to machine fetchers.

Coverage

Medium

Treat this profile as payment and invoicing API comparison context, not as complete coverage of crypto data, chain state, or PubFi runtime routing.

Use cases

  • Compare Request Network payment workflow evidence before runtime integration work

Comparison snapshot

Request Network API should be compared as payment workflow infrastructure. It can remain useful for Discovery evaluation context, but it should not compete as an ordinary crypto data-source provider or receive high-confidence LLM export treatment.

PubFi friction relief

Docs

Source friction
Request Network API docs expose payment request, payout, crypto-to-fiat, compliance, supported-chain, and webhook evidence.
PubFi relief
PubFi Discovery keeps Request visible as guarded payment API context while separating it from data-source and gateway certification claims.

FAQ

Is Request API available through the PubFi gateway?

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