A developer or agent needs to find a crypto data API for a workflow.

User Need

“I need a data source for wallet labels, token balances, governance proposals, market prices, or chain-specific data. I need to compare source fit before integrating.”
  1. Start with the Discovery overview.
  2. Use the source directory to search and filter providers, or continue by category, chain, comparison, or topic.
  3. Read public status, source freshness, auth/pricing posture, and claim-safe notes.
  4. Use related pages and Markdown mirrors for agent-readable context.
  5. If the workflow needs execution, inspect the current Registry v2 catalog and plan an exact path and method.

Good Fit

Discovery is useful when the user needs:
  • source lists;
  • alternatives and comparisons;
  • chain-specific coverage;
  • topic-led guidance;
  • public docs and OpenAPI pointers;
  • source freshness and claim-safety context.

Not A Fit

Discovery is not proof that PubFi can execute every listed provider route. Execution belongs to the current Registry and request-time readiness gates. Continue with Source Evaluation when you need a structured integration decision.