Data & API teams
Share the public context behind your data, documentation, coverage, and intended use cases. PubFi can explore how that source should be represented in Discovery and whether a separate integration review makes sense.
Partner with PubFi to bring better crypto data into agent workflows
PubFi works with data and API teams, chains and ecosystems, and technology platforms exploring better ways to make crypto data discoverable, usable, and ready for agent-driven products
Start with the context your team already owns
Chains & ecosystems
Explore the data developers and agents need across your ecosystem, where discovery is fragmented, and which public resources should be easier to evaluate.
Technology & distribution
Explore technical integrations, developer education, and distribution paths that help teams find and use crypto data in their existing workflows.
A focused conversation, not a one-size-fits-all program
Share context
Tell PubFi what your team provides, who it serves, and what you want to explore.
Review fit
PubFi considers the product, technical, and ecosystem context relevant to the inquiry.
Define a next step
If there is a useful fit, both teams can agree on the appropriate follow-up.
Partnership questions
- Who should contact PubFi about a partnership?
- Data and API teams, chains and ecosystem organizations, and technology platforms can contact PubFi when they have a specific data, integration, or distribution context to explore.
- Can a data provider ask to be included in Discovery?
- A provider can share public source and documentation context for review. An inquiry does not guarantee a Discovery profile, Registry acceptance, or gateway availability.
- Is a Discovery listing the same as a PubFi partnership?
- No. Discovery describes public data sources and demand context. A partnership is a separate organizational relationship, and neither status proves that an API is executable through PubFi.
- What should we include in an inquiry?
- Include your organization, public product or documentation links, the audience you serve, relevant data coverage, and the outcome you want to explore. Do not send credentials or private provider data by email.
Explore what a useful partnership could look like
Share your context, the teams you serve, and the outcome you want to explore