01
Useful routing
The page points people to the right product area instead of a generic inbox.
COMMUNITY
A serious API marketplace needs visible feedback loops.
Use community routes to follow roadmap direction, send provider feedback, surface buyer needs and keep product questions connected to public evidence.
Community
oanor.com
Find
Useful routing
Resolve
Context first
Share
Public feedback
Operational promise
Help and community are practical entry points: documentation, support, roadmap and feedback all link back to working product surfaces.
02
Context first
Support requests become easier when users know what evidence to include.
03
Public feedback
Community input connects buyer questions and provider improvements.
How it works
A practical assistance workflow
Start with self-service evidence, then escalate with enough context for a useful answer.
1
Check the obvious signal
Open status or docs before guessing at the cause.
2
Inspect your account path
Review keys, subscriptions, team access or provider setup as needed.
3
Use the right channel
Send product, provider, security or support questions through the relevant route.
4
Close the loop
Use roadmap and feedback paths to turn repeated issues into product improvements.
Proof points
Useful checks before you commit
Docs route
Documentation is linked directly so integration questions start with examples.
Status route
Live platform status stays visible before filing incidents.
Contact route
Human support remains available for account, billing and security context.
Roadmap route
Community feedback has a visible product direction to attach to.