Teach the product
The resource hub should explain Joe clearly enough that new visitors understand the value quickly.
RESOURCES
Resources
Research, documentation, status, and guides that explain the product and help teams launch with confidence.
Research
Documentation
Status and guides
INTENTIONRESOURCES
TASK LAYERLEARN
OUTCOMEEverything teams need to launch
LEARN
Everything teams need to launch
Use the resources section to understand the model, implementation path, and operating expectations before you go live.
What the resource hub should do
A visitor reads the research, reviews the docs, checks operational status, and then books a demo once the product story makes sense.
Reduce implementation risk
Docs and guides should help teams build the right thing the first time.
Show operational confidence
Status and support pages make the platform feel real and dependable.
Lead to action
Every resource should make it easier to book a demo or start the integration.
Research
Understand the thinking behind Joe.
Joe’s research explains why task graphs, verification, and durable context matter when AI is expected to finish work.
Research
Understand the thinking behind Joe.
- LIM vs LLM
- Task economy
- Verification
Documentation
Build with a clear implementation path.
Docs should show how to connect Joe, create tasks, handle states, and ship a product that returns completed outcomes.
Documentation
Build with a clear implementation path.
- Quickstart
- API reference
- Integration guides
Status
See what is running right now.
A status page gives teams confidence that the API, runtime, and connected applications are available when work needs to move.
Status
See what is running right now.
- Service health
- Runtime availability
- Operational visibility
Guides
Learn how to launch Joe in real products.
The guides help teams move from first idea to product launch without losing the link between product story and implementation details.
Guides
Learn how to launch Joe in real products.
- Internet of Agents
- Joe Connect guide
- Build with Joe
EXAMPLE
How a team uses the resources hub
A visitor reads the research, reviews the docs, checks operational status, and then books a demo once the product story makes sense.
1Read the overview
A visitor reads the research, reviews the docs, checks operational status, and then books a demo once the product story makes sense.
2Check the documentation
A visitor reads the research, reviews the docs, checks operational status, and then books a demo once the product story makes sense.
3Review status
A visitor reads the research, reviews the docs, checks operational status, and then books a demo once the product story makes sense.
4Study the guides
A visitor reads the research, reviews the docs, checks operational status, and then books a demo once the product story makes sense.
5Book a demo
A visitor reads the research, reviews the docs, checks operational status, and then books a demo once the product story makes sense.
BOOK A DEMO
Resources should move people forward.
If your team wants the full implementation story, start with the resource hub and then book a demo.