# guide > Return the client guide in full, as Markdown: what the corpus is and what it cannot tell, how to read every field and band, what each call costs… Return the client guide in full, as Markdown: what the corpus is and what it cannot tell, how to read every field and band, what each call costs and spends, the recommended order of work, recipes for common questions and how to report results to your user. Free. Read it before you write code against the API, and whenever you are unsure how to read a field or what a call will cost. ## Request ```text POST https://api.megido.io/v1/tools/guide ``` Headers: `Authorization: Bearer `, and with a body `Content-Type: application/json`. The tool's arguments; {} or no body for none. Its JSON Schema: ```json { "type": "object", "properties": {}, "additionalProperties": false } ``` ## Answers | Status | Answer | |---|---| | 200 | The tool's answer: `GuideAnswer` | | 400 | The request cannot be served as sent: `bad_request`, `invalid_params` | | 401 | No key, or a key the API does not take: `unauthorised` | | 413 | The body is larger than the API takes: `bad_request` | | 415 | The body is not sent as application/json: `bad_request` | | 429 | Too many calls: `rate_limited` | | 500 | The call failed on Megido's side: `internal_error` | | 503 | Not available just now: `service_unavailable`, `lock_timeout` | Every error has the body `{"error": {"code": "…", "message": "…"}}` with the details of its code. The OpenAPI document holds every schema: https://api.megido.io/v1/openapi.json.