> For the complete documentation index, see [llms.txt](https://programmable.market/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://programmable.market/docs/infrastructure/status.md).

# Service status

Check launch availability, request progress and indexing freshness

Use the status interface for the operation you are performing. API availability, a launch's progress and the freshness of an index are separate states. A successful HTTP response does not by itself establish that a new request can be authorized or that a feed has reached the current finalized block.

| Service                | Status source                                                                                                                                  |
| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| Module Mode            | [Active engine and catalog](https://programmable.market/api/module-mode)                                                                       |
| Custom Launch API      | [API readiness](https://api.programmable.market/readyz) and [product discovery](https://programmable.market/.well-known/programmable.json)     |
| Robinhood V4           | [Chain readiness](https://api.programmable.market/v4/chains/4663/readiness)                                                                    |
| Robinhood MultiRole    | [Capabilities](https://api.programmable.market/v4/chains/4663/multi-role-custom-launches/capabilities) and the context linked by that response |
| Ethereum Developer API | [Index status](https://developers.programmable.family/api/v2/status)                                                                           |

## Launch requests

Use the status URL returned for your request. V4 and MultiRole have separate clients and resource contracts. Follow the reported remediation when evidence is missing; only an authorized wallet handoff is ready for transaction review. The [Custom Launch quickstart](/docs/developers/custom-launch-quickstart.md) explains API keys, retries and the wallet step.

For Robinhood V4, discovery must report `publicWrites`, `publicAuthorization` and `releaseReady` for both the version and chain entry. Match the ready release to the immutable client release in discovery. MultiRole supplies its own context, readiness and economic verification. The [complete API reference](/docs/developers/custom-launch.md) defines the detailed lifecycle and error codes.

## Indexed data

Check the source's finalized checkpoint, scan coverage, cursor completion and data-quality fields. Preserve an existing verified launch if a price or chart provider is unavailable. Keep stale or missing market values explicitly marked rather than guessing replacements.

[Module Mode indexing](/docs/developers/module-mode-indexing.md), [Robinhood Custom indexing](/docs/developers/robinhood-terminal-indexer.md) and the Ethereum status endpoint publish their own freshness and verification rules. Source verification follows finality and does not change the transaction's finality result. External terminals determine their own ingestion and trading support.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://programmable.market/docs/infrastructure/status.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.