# Retrieve agent config `GET /api/v1/agent-config` How this store's assistant is configured: whether it runs at all, its name, greeting and persona, the two instruction directives, the three skill groups, and the merchant's starter chips. A SINGLETON, so there is no id and no page block. A STORE THAT HAS NEVER CONFIGURED THE ASSISTANT IS NOT A 404. It answers the documented defaults, which are what the assistant is actually running with: enabled true, no custom voice, both directives and all three skills on. Its updated_at is null, because there is no row to have a version, and that null is what you send back as expected_updated_at on your first write. enabled is the whole gate. The storefront widget renders on exactly this, so false means shoppers see nothing whatever else is set. persona_instructions is published here and withheld from the storefront's own shopper-facing config. It shapes tone only: the server always appends its safety rules on top, so a persona can never remove a guardrail. ## Responses - `200` — Success - `400` — The request was refused before any state changed. `code` is one of: `invalid_body`, a write body this route will not take. `reason` partitions it and `field` names the key when one key is at fault. `invalid_query`, a query parameter, including limit and after. `invalid_text`, a NUL byte or bytes that are not valid UTF-8 anywhere in the path, the query or the body. Strip control characters before sending. `idempotency_key_required`, a write sent without the Idempotency-Key header. `invalid_request`, an Idempotency-Key longer than 255 bytes. Routes add their own codes for rules only they know. Switch with a default arm. - `401` — No credential, or one this API does not accept. `code` is always `unauthorized`. THE BODY IS DELIBERATELY UNINFORMATIVE. An expired key, a revoked key, a publishable key, a key belonging to another merchant and a key that never existed are all refused with the same bytes, so this response cannot be used to probe which keys exist. Check the key's state in the dashboard rather than inferring it here. Send the key as `Authorization: Bearer ` or as `X-API-Key: `. It is never accepted in a query string. - `403` — The key lacks the read_sales_agent scope. `code` is `insufficient_scope` and the message names the scope to ask the merchant for. - `429` — Too many requests. `code` is `rate_limited`. Two limits apply independently: one on the credential and the route family, one on the client address. The headers describe whichever has less left, so honouring Retry-After always clears the window that bound. - `default` — Any status this operation does not list, in the same envelope. A 5xx means the request may or may not have applied. Retry it with the SAME Idempotency-Key: that is the only way to find out without risking a duplicate, and it is what the key is for. A few 4xx conditions arrive here rather than as a listed status because they depend on the merchant's plan or on a module being wired: 402 when a quota or a plan limit is reached, and 503 when a capability the route needs is not configured on this deployment. Both carry a `code` naming which. ## Example ```bash curl --request GET \ --url 'https://api.mercemur.com/api/v1/agent-config' \ --header 'Authorization: Bearer ' ```