Direct Answer
Use a wallet labels API when an agent needs address, entity, portfolio, or risk context before deciding what to fetch next. Wallet and portfolio APIs fit account holdings, entity-intelligence sources fit labels and attribution, and compliance APIs fit screening or risk workflows. PubFi Discovery maps those source classes and keeps public source inclusion separate from live PubFi routeability.
- Query ownership
- wallet labels API; cross-chain wallet labels API; what API can an AI agent use for wallet labels; why my agent cannot find wallet labels; agent cannot fetch wallet labels
- Safe citation boundary
- Indexed-only. Use this page to compare wallet-label, wallet-portfolio, on-chain analytics, and screening sources by public evidence, chain coverage, auth, and agent-readable contract shape. Discovery inclusion is source-selection evidence only; it is not a claim that PubFi provides a universal wallet-label gateway, supplier route, or automated risk decision system.
- Readback boundary
- Ranking and AI-citation success require Search Console, public SERP, Bing/Webmaster, Vercel, and answer-engine readbacks; this page does not claim those outcomes by itself.
Source Fit Summary
A wallet labels API should be evaluated by entity coverage, chain support, attribution rules, freshness, and whether labels are suitable for automated agent decisions. PubFi Discovery compares wallet, entity, compliance, and analytics sources without claiming that every listed source is currently routed through PubFi.
- Primary query
- wallet labels API
- Supporting queries
- cross-chain wallet labels API; what API can an AI agent use for wallet labels; why my agent cannot find wallet labels; agent cannot fetch wallet labels
- Query group
- Wallet labels and entity intelligence APIs
- Best starting page
- This page
- Availability status
- Indexed-only
- Demand signal
- agent workflow
Source Evidence
Use this page to compare wallet-label, wallet-portfolio, on-chain analytics, and screening sources by public evidence, chain coverage, auth, and agent-readable contract shape. Discovery inclusion is source-selection evidence only; it is not a claim that PubFi provides a universal wallet-label gateway, supplier route, or automated risk decision system.
- Moralis wallet and address API profile
- Zerion wallet portfolio API profile
- Nansen API public provider profile
- Recurring SERP and answer-engine snapshot
Agent Use Cases
- Wallet triage agent
- Use wallet-label and portfolio sources when an agent needs to understand an address, holdings, activity, or possible entity context before choosing a deeper data source.
- Entity-intelligence agent
- Use entity and on-chain analytics sources when the workflow needs attribution, tagged counterparties, or wallet-cluster context with clear provenance and freshness expectations.
- Risk-screening handoff
- Use compliance or identity-adjacent sources only after separating public Discovery evidence from any regulated, risk-scoring, KYC, or screening decision that needs product-runtime approval.
- Agent-readable source selection
- Use this topic together with /agents.md, /llms.txt, and /llms-full.txt so an agent can select wallet-label source classes without assuming a universal PubFi execution route.
Comparison Criteria
- Label type and provenance
- Separate exchange, contract, entity, token-holder, portfolio, and risk labels, then require visible source evidence or update cadence before letting an agent reuse the label.
- Chain and address coverage
- Check whether the source covers Ethereum, Bitcoin, Solana, EVM chains, or a narrower dataset before using it for cross-chain wallet-label workflows.
- API contract and auth
- Prefer sources with documented endpoint families, API-key handling, rate-limit notes, SDKs, or examples that an agent can inspect before planning a request.
- Portfolio versus label fit
- Use wallet-portfolio APIs for balances and positions, entity-intelligence APIs for labels and attribution, and screening APIs for risk workflows; do not treat those source classes as interchangeable.
- Claim safety boundary
- Discovery can say which public sources may fit wallet-label work, but it cannot claim a PubFi wallet-label gateway or AI citation until gateway readiness and answer-engine readback prove it.
Limits And Boundaries
- No universal label source
- Wallet labels differ by chain, entity methodology, freshness, commercial access, and legal use case, so agents should keep fallback source classes visible.
- Risk decisions need product gates
- Compliance, sanctions, fraud, KYC, or risk-scoring usage requires product-runtime and policy review beyond this Discovery topic.
- Routeability is source-specific
- A source profile can be useful for Discovery before any source-specific production route evidence exists.
- Ranking and citation are not inferred
- This topic resolves query ownership for wallet-label demand, but Google ranking and ChatGPT, Claude, Perplexity, or AI search citation require fresh readback evidence.
Related Discovery Records
FAQ
What API can an AI agent use for wallet labels?
Start by separating the workflow. Wallet and portfolio APIs help with balances, positions, and account context; entity-intelligence and on-chain analytics sources help with labels and attribution; compliance APIs help with screening workflows. PubFi Discovery compares those source classes without claiming every source is executable through PubFi.
Why can my agent not fetch reliable wallet labels?
Wallet labels are not one universal dataset. Coverage, chain support, label methodology, freshness, auth, and permitted use vary by provider, so an agent should select the source class first and keep provenance visible before relying on a label.
Which sources should I compare for wallet labels?
Compare wallet and portfolio sources such as Moralis and Zerion with entity or analytics sources such as Nansen and Allium, plus compliance-oriented sources such as Scorechain or Persona when the workflow requires screening context.
Does PubFi provide a wallet labels gateway today?
This page is a Discovery owner for wallet-label source selection. It should not be read as a universal PubFi gateway claim unless a source-specific gateway readiness record and production route prove that availability.
Demand Signal
PubFi can record interest in this source-selection workflow without storing payment proofs, wallet data, raw search queries, or procurement notes.
Compare wallet-label sources