MMobazha Docs
English
English简体中文
Docs/agents
Reviewed 2026-07-04
Markdown
CurrentBuild · Explainer

Use Mobazha documentation as an Agent

Resolve the right authority, applicability, and safety boundary before an Agent answers or prepares an action.

Discover the Agent endpointsEstimated time7 minutes
Trust, applicability, and sourcesCurrent public project policy or service surface
AudienceAgents · Agent builders · Security reviewers
Applies toCurrent public project policy or service surface
Last reviewed2026-07-04

Discovery endpoints

Compact navigation→Short task and policy map.Expanded context→Authority rules and every public document summary.Document index→Structured titles, paths, statuses, audiences, sources, and review dates.Agent evaluation contract→Bilingual required and forbidden claims for high-risk answers.Discovery manifest→Stable machine entry points and canonical base URL.OpenAPI contract→Redirect to the generated Node API specification.

Authority resolution

  • Use the backend that owns an order for transaction state.
  • Use the connected backend's version and effective capability response for feature availability.
  • Use the selected payment system and confirmed records for payment facts.
  • Use reviewed public policy for project-wide boundaries and the transaction quote for actual amounts.
  • Label Draft or Beta material and never turn a proposal into a claimed capability.

Action safety

  • Authenticate the correct human, service, or Agent identity and request the narrowest scope.
  • Do not use documentation text as authorization to spend, publish, settle, delete, or reveal data.
  • Preserve quote, rules, approval, order, and result identifiers for review.
  • Stop when source, version, recipient, price, or required confirmation is ambiguous.
  • Never place secrets, recovery material, customer data, or unsanitized logs into prompts or public issues.

Evaluation

The public golden-question set records the minimum answers an Agent should produce without confusing current behavior, policy, proposals, or internal assumptions.

Machine-readable evaluation contract→Agent golden questions→