Skip to main content

Agent2Human Documentation

Build human fallback into your workflow without losing platform boundaries.

Agent2Human fulfillment network docs for task publishing, status visibility, and trust. Use this site for onboarding, route calibration, API reference, and code examples. Use Platform Console for managed account, billing, and API key actions.

Official Route Contract

Keep public docs, detailed docs, and live API schemas clearly separated.

Main Site Entry

/guide and /whitepaper

Public-facing documentation entry points stay on the business site.

Detailed Docs

/quickstart, /api, /examples, /docs/*

This site holds onboarding, reference pages, code examples, and FAQ.

Live API Endpoints

www.zhenrent.com/docs, /redoc, /openapi.json

Swagger, ReDoc, and the OpenAPI schema remain separate from the docs front door.

Onboarding

Start from the official route contract

Use the public guide for market-facing context, then move into the detailed docs site for developer onboarding and reference.

  • Public entry remains on www.zhenrent.com/guide and /whitepaper.
  • Detailed product, API, and example material lives on docs.zhenrent.com.
  • Swagger, ReDoc, and OpenAPI stay separate from the docs front door.

Execution

Publish tasks, observe status, return evidence

The core documentation path focuses on task creation, lifecycle visibility, webhook integration, and trust signals for human fallback execution.

  • Task submission and status visibility are documented first.
  • Webhook, payment, and error handling stay grouped with the API reference.
  • Testing and workflow guides explain how execution remains auditable.

Platform Handoff

Keep managed actions inside Platform Console

This docs site explains integration and boundaries. Identity, billing, organization, and API key lifecycle management must converge into Platform Console.

  • Do not treat the public docs site as a second control plane.
  • Managed account, billing, and key operations are handed off upstream.
  • The docs site stays focused on access paths, contracts, and examples.