inuit Agency API
The inuit Agency API gives programs and AI agents read-only access to the public content of www.inuit.agency, the website of inuit Agency (inuit GmbH), a brand consultancy in Hamburg, Germany. It returns JSON, needs no API key and has no write operations.
- Base URL:
https://www.inuit.agency/api/v1 - OpenAPI description: https://www.inuit.agency/openapi.json
- API catalog (RFC 9727): https://www.inuit.agency/.well-known/api-catalog
- Site guide for agents: https://www.inuit.agency/llms.txt
Authentication
None. All endpoints are public and accept GET, HEAD and OPTIONS. Responses allow cross-origin requests (Access-Control-Allow-Origin: *).
Endpoints
| Request | Returns |
|---|---|
GET /api/v1 | API index: version and links to all endpoints. |
GET /api/v1/pages | List the public pages, case studies and articles. Optional parameter: section. |
GET /api/v1/pages/{slug} | Read one page or article as JSON, including its Markdown text. Use "index" for the homepage. |
GET /api/v1/pages/portfolio/{slug} | Read one case study as JSON, including its Markdown text. |
GET /api/v1/search | Full-text search. Required parameter: q. Optional parameter: limit. |
GET /api/v1/contact | Company name, address, phone, email and official profiles. |
List pages
The parameter section accepts all (default), pages, case_studies or articles.
curl -sS "https://www.inuit.agency/api/v1/pages?section=case_studies"
Read a page
Use the slug of the page, as in its URL path. The homepage has the slug index. Case studies use /pages/portfolio/{slug}. The field markdown holds the full text with YAML frontmatter.
curl -sS "https://www.inuit.agency/api/v1/pages/solutions"
{
"title": "Solutions",
"type": "page",
"url": "https://www.inuit.agency/solutions/",
"markdown_url": "https://www.inuit.agency/solutions.md",
"api_url": "https://www.inuit.agency/api/v1/pages/solutions",
"summary": "...",
"last_updated": "2026-01-01T00:00:00Z",
"markdown": "---\ntitle: ..."
}
Search
The parameter q is required (2 to 100 characters). The parameter limit accepts 1 to 10, default 5.
curl -sS "https://www.inuit.agency/api/v1/search?q=brand%20strategy&limit=3"
Contact details
curl -sS "https://www.inuit.agency/api/v1/contact"
Errors
Errors use the format of RFC 9457 with the media type application/problem+json. Every error has a stable code and a resolution that says what to do next. Requests for pages that do not exist on the website return the same format when the request sends Accept: application/json.
{
"type": "https://www.inuit.agency/developers/#error-page-not-found",
"title": "Page not found",
"status": 404,
"detail": "No public page exists at the path \"does-not-exist\".",
"instance": "/api/v1/pages/does-not-exist",
"code": "page_not_found",
"resolution": "List valid paths with GET https://www.inuit.agency/api/v1/pages or search with GET https://www.inuit.agency/api/v1/search?q=<terms>.",
"documentation_url": "https://www.inuit.agency/developers/#errors"
}
| Code | Status | Meaning | Resolution |
|---|---|---|---|
invalid_parameter | 400 | Invalid parameter | Correct the parameters named in "invalid_params" and retry. Allowed values are listed at https://www.inuit.agency/developers/#endpoints. |
not_found | 404 | Not found | Use https://www.inuit.agency/llms.txt or https://www.inuit.agency/wp-sitemap.xml to find valid URLs, or search with https://www.inuit.agency/api/v1/search?q=<terms>. |
page_not_found | 404 | Page not found | List valid paths with GET https://www.inuit.agency/api/v1/pages or search with GET https://www.inuit.agency/api/v1/search?q=<terms>. |
route_not_found | 404 | API route not found | Use one of the routes listed by GET https://www.inuit.agency/api/v1 or described in https://www.inuit.agency/openapi.json. |
method_not_allowed | 405 | Method not allowed | This API is read-only. Send a GET or HEAD request. |
internal_error | 500 | Internal error | Retry after a short pause. If the error persists, contact hamburg@inuit.agency. |
Versioning and deprecation
- The version is part of the URL path. The current and only version is
v1. - Changes within a version are backwards compatible: new endpoints, new optional parameters and new response fields. Clients should ignore fields they do not know.
- Changes that break existing clients are released under a new version path.
- Before a version is retired, its responses carry the headers
Deprecation(RFC 9745) andSunset(RFC 8594) and this page states the date.
Rate limits and caching
- The API has no API keys and no quota per client.
- The hosting platform limits bursts of requests. It can answer with status 429 or 503 and a
Retry-Afterheader. Wait for the stated time before retrying. - Send requests one after another and reuse responses. Successful responses allow caching for five minutes (
Cache-Control: public, max-age=300).
Other ways to read the site
- Markdown: append
.mdto any page path (homepage:/index.md) or send the headerAccept: text/markdown. - MCP server: inuit Agency MCP server with the same content as tools for AI assistants.
- XML sitemap: https://www.inuit.agency/wp-sitemap.xml
Contact
Questions about the API: hamburg@inuit.agency. Company details are on the contact page and in the imprint.