Start self-serve
Best when you want to reserve a handle, build the public trust page, and evaluate the identity workspace directly.
Create accountContact
Choose the fastest route into verified identity work.
Most teams get the best answer by starting with the right path: build the identity, compare access, read the integration references, or open a concrete technical thread.
Self-serve onboardingPricing and accessIntegration planningTechnical support
Contact paths
Start where the decision is blocked.
pox.me is built to be self-serve first, with support paths for pricing, integrations, and rollout questions once the workflow is concrete.
Choose access
Best when the question is pricing, workspace entitlement, checkout, or how much identity capacity to activate.
Open pricingPlan an integration
Best when your team needs API catalog, OAuth metadata, MCP surfaces, or agent-ready product discovery.
Read docsOpen a technical thread
Best when you have a specific bug, integration question, protocol issue, or developer-facing rollout detail.
Open GitHubRecommended order
Make the conversation concrete before it becomes a support thread.
The highest-signal support requests point to an identity, a plan, an integration path, or a repeatable workflow decision.
What to include
If you need human follow-up, include the identity handle, the target workflow, the credential or access state involved, and the exact action that is blocked.
Create or identify the pox.me handle involved in the workflow.
Confirm whether the question is about public profile, credential proof, private access, billing, or integration.
Use docs and protocol references first for machine-readable discovery and OAuth/MCP planning.
Open a team conversation only when the next decision cannot be resolved inside the product.
Still evaluating?
Build a real profile instead of debating the abstract workflow.
A live identity page makes the product easier to judge: profile quality, proof, contact routing, and private controls become visible immediately.