Account and identity setup
Use this path when sign-up, sign-in, recovery, handle creation, visibility, or profile publishing is blocked.
Help
Unblock identity setup, proof, billing, and agent access faster.
Most issues map to one of four areas: account setup, credential proof, plan access, or integration route. Start with the closest support area and keep the affected identity handle handy.
Account setupCredential statusBilling accessAgent integrations
Support areas
Find the blocker by workflow.
The quickest fix usually comes from identifying which part of the identity system owns the state you are seeing.
Credential verification
Use this path when email, wallet, social, Telegram, LinkedIn, or credential binding status does not look right.
Plan and access
Use this path when billing, checkout, entitlement, protected workspace, or API access is the likely blocker.
Integration and agent access
Use this path when OAuth metadata, public discovery, MCP tools, or machine-readable references are involved.
FAQ
Common questions about pox.me.
These answers are written for high-intent users evaluating verified identity pages, credential proof, private workspace controls, and agent-ready access.
Can I build a public identity page before everything is verified?
Yes. You can start with the public profile and add verified credential proof as each signal becomes ready.
Why does a credential need verification before it appears as trusted proof?
Verification helps the public page distinguish a claim from a proven signal, which keeps the trust surface clearer for visitors.
Do private workspace settings appear on the public profile?
No. Public identity presentation and private workspace operations are connected, but you choose what becomes visible.
Can software agents use pox.me after payment and authentication?
Yes. Agent and product clients should use the published discovery, OAuth, protected resource, and MCP references once access is ready.
Where should I start if a page, form, or status looks stale?
Try the action again from the workspace first. pox.me uses optimistic UI and event-driven refresh paths, but backend confirmation still controls durable state.
Before opening a thread
A good support request includes the state that changed.
For identity and credential issues, the important details are usually the identity handle, credential type, expected state, current state, and the action that triggered the mismatch.
Include the identity handle and action
For example: the handle, whether you added or removed a credential, which provider was involved, what status stayed stale, and whether the issue appears in public preview or the authenticated workspace.
Need more context?
Use docs for integration questions and contact for rollout-specific blockers.
If the issue is product setup, start with the app. If the issue is software access, start with docs and protocol references. If the issue is a rollout decision, contact the team with the exact workflow.