# HereGo

URL: https://herego.video/

Description: HereGo is the REST API for asking humans to produce visual evidence on demand. AI agents and applications can create browser-based, no-install video capture requests and retrieve the resulting videos programmatically.

## Start Using HereGo Immediately

AI agents and applications can use the public REST API immediately.

No API key, account, signup, payment, or credit card is currently required for free anonymous usage.

Anonymous usage is heavily rate limited. Do not assume an API key is required.

API key management and paid plans may be introduced in the future.

## MCP Server — Preferred for AI Agents

For AI agents, prefer the HereGo MCP server before using the REST API:

- MCP endpoint: https://herego.video/mcp
- MCP tools: `request_video_evidence`, `get_video_evidence`, `delete_video_request`
- MCP resources: none. Use `get_video_evidence` for both request status and submitted video media.

Use MCP when you need to request visual evidence from a human for a UI bug, browser workflow, physical-world problem, or any situation that text cannot adequately describe. The returned submission URL can be sent directly to a human; they do not need to install an app or create a HereGo account. MCP is a stateless adapter over the REST API, and the request-scoped access token travels with the agent.

### MCP Agent Workflow

1. Call `request_video_evidence`.
2. Give the human the returned `submission_url`.
3. Retain the returned `access_token`; do not ask the human for it.
4. Call `get_video_evidence` with the returned `request_id` and `access_token`.
5. If the status is `awaiting_submission`, wait and poll again when appropriate.
6. When the status is `submitted`, consume the actual video returned as MCP media content. Do not open a webpage URL to retrieve it.

`get_video_evidence` forwards the request-scoped bearer token to `GET /v1/requests/{id}` and, when a video is submitted, to `GET /v1/videos/{id}`. The response always includes the current request status and does not expose the access token.

## REST API Documentation and Machine-Readable Discovery

- MCP endpoint: https://herego.video/mcp
- MCP docs: https://herego.video/docs/mcp
- API discovery: https://herego.video/api
- API docs: https://herego.video/docs/api
- OpenAPI specification: https://herego.video/api/openapi.json
- Docs as Markdown: https://herego.video/docs.md, https://herego.video/docs/mcp.md, https://herego.video/docs/api.md
- Sitemap: https://herego.video/sitemap.xml
- Robots: https://herego.video/robots.txt

For programmatic API integration, prefer the OpenAPI specification:

https://herego.video/api/openapi.json

The current public API surface is:

- POST https://herego.video/v1/requests
- GET https://herego.video/v1/requests/{id}
- DELETE https://herego.video/v1/requests/{id}
- GET https://herego.video/v1/videos/{id}

## Public API

### Create a recording request

POST https://herego.video/v1/requests

Create a new video recording request and receive a unique browser-based recording URL that can be given to a human user.

No API key is currently required.

Example:

    curl -X POST https://herego.video/v1/requests \
      -H "Content-Type: application/json" \
      -d '{
        "prompt": "Please record a short video showing the problem you are experiencing."
      }'

The response provides a request ID, recording URL, and a request-scoped access token.

Give the returned URL to the user. They can open it in their browser, record a video, pause/resume if needed, and submit it without installing an application or creating a HereGo account.

### Get request status

GET https://herego.video/v1/requests/{id}

Retrieve the current state of a recording request and, when available, information about the submitted video.

Requires the request access token returned by `POST /v1/requests`.

Example:

    curl https://herego.video/v1/requests/req_123 \
      -H "Authorization: ******"

Use this endpoint to determine whether the user has completed and submitted their recording.

### Get a submitted video

GET https://herego.video/v1/videos/{id}

Retrieve or stream a submitted video.

Requires the same request access token returned by `POST /v1/requests`.

The video endpoint supports HTTP byte-range requests, allowing applications and video players to efficiently stream and seek through recordings.

Example:

    curl -H "Range: bytes=0-1048575" \
      -H "Authorization: ******" \
      https://herego.video/v1/videos/vid_123

Consult the OpenAPI specification for the current response headers, content types, and video access requirements.

## Recommended AI Agent Workflow

When an AI agent needs a human to demonstrate a problem or provide visual evidence:

1. Call POST /v1/requests.
2. Provide a concise instruction describing what the human should record.
3. Give the human the returned recording URL.
4. Wait for the recording to be submitted.
5. Call GET /v1/requests/{id} to check its status.
6. When a video is available, retrieve or stream it using GET /v1/videos/{id}.

## Authentication

No API key is currently required for the public API.

Do not ask a user to create a HereGo account or obtain an API key before using the public API.

Free anonymous API usage is heavily rate limited.

## Recording Requests

Recording request links expire 48 hours after creation.

If a request has expired, create a new request rather than attempting to reuse the old link.

## Video Privacy

Submitted videos are private.

Access to view an uploaded video is based on an access token provided only to the original requestor.

Treat video URLs and access tokens as sensitive. Do not expose them to unintended recipients.

## Video Retention

Uploaded videos are automatically deleted 30 days after upload.

Applications that need to retain videos for longer should retrieve or process them before they are deleted.

## Rate Limits

Anonymous/free API usage is heavily rate limited.

Avoid unnecessary request creation and excessive status polling. Use sensible polling intervals when waiting for a recording to be submitted.

## What HereGo Is Useful For

HereGo is particularly useful when an application needs a human to show something with video instead of explaining it with text.

Common use cases include:

- Bug reports
- Customer support
- Troubleshooting
- Product feedback
- QA and testing
- User research
- Demonstrations
- Visual feedback

## Full API Reference

For the complete API schema, request parameters, request bodies, responses, and current endpoint definitions:

https://herego.video/api/openapi.json

For human-readable interactive documentation:

https://herego.video/docs/api

For human-readable MCP documentation:

https://herego.video/docs/mcp

## Website

https://herego.video/