# HTTP and Market Monolith

Availability: Instructions published.
Connection status: Connection not available.

Last reviewed: 2026-08-28.

Use HTTP to understand the authentication release contract without choosing a client library. These instructions do not activate a connection.

## The request boundary

After the authentication release is confirmed, send `GET /v1/me` to `https://api.marketmonolith.com` with the `X-Market-Monolith-Key` header. Use HTTPS and keep the secret outside URLs, browser code, shared command history and screenshots.

```sh
curl --request GET --max-time 15 \
  --url https://api.marketmonolith.com/v1/me \
  --header "X-Market-Monolith-Key: $MARKET_MONOLITH_API_KEY"
```

The environment variable must come from your protected secret setup, not a hardcoded value. The response identifies an account, application and key; it does not authorize business actions or charge credits.

## Before using a command-line client

The [curl manual](https://curl.se/docs/manpage.html) documents request headers, timeouts and redirect handling. Use your environment's approved secret-injection method. A literal secret in a command argument may be visible in shell history or process listings.

Set a bounded timeout. Do not enable verbose traces containing authorization headers. Do not follow an unexpected redirect with the secret attached.

## Read the outcome

Check the HTTP status before parsing JSON. Compare the returned account and application to the developer console. A successful authentication check is not a business-operation result.

For a failure, retain the safe request identifier and status, not the key or full request headers. Avoid automatic retry loops. See [Errors and troubleshooting](/docs/errors-troubleshooting).

## Support boundary

Market Monolith owns its published request contract; your HTTP client owns its local installation and behavior. No native client package is required. Connection availability remains separate from these published instructions.