---
url: https://ora.ai/docs/journeys
title: "Agent journeys - Docs"
description: "What a journey run is, the keyless curated tier and its caps, and how to get a partner key for custom tasks."
crawled_at: 2026-10-18T19:27:05Z
ask: https://ora-ai.ora.run/ask
docs: https://ora-ai.ora.run/.well-known/ora/docs
lang: en
---
# Agent journeys

A journey sends a real agent at a live site on a concrete task and records the full trajectory: every page it reads, every tool call, where it succeeds and where it gets stuck. It is the engine behind ora.ai/journey , where curated runs are public.

Custom tasks are gated

A journey run drives a real agent for minutes, not milliseconds, so the journey API is capped and custom tasks need a key. Without one you can run any curated intent against any domain (100 runs per target, 20 per IP, and 3000 across all anonymous callers in a rolling 24 hours): browse runs on

ora.ai/journey

or start one from the CLI with

deep-journey --intent

.

Contact us

for a partner key to run journeys on your own tasks (

deep-journey --task

). Key holders integrate journeys with the

partner guide

.

# Footer

The standard for agent experience.

© 2026 [era labs](https://eralabs.ai/)

Product

- Scan a site

- [Journey](https://journey.ora.ai/)

- [WebMCP audit](https://webmcp.ora.ai/)

- [Directory](https://directory.ora.ai/)

Resources

- Methodology

- Research

- Blog

- API Docs

Company

- About

- Contact

- Privacy

- [@oradotai](https://x.com/oradotai)
