# Glimps developer resources

This is the canonical machine-readable entry point for agents and developers integrating with Glimps.

The human-readable developer documentation index is available at https://useglimps.com/docs/.

## Public read-only resources

- [OpenAPI description](https://useglimps.com/openapi.json) — schema for the public JSON and text endpoints.
- [Structured product data](https://useglimps.com/agent-data.json) — company, product, pricing, features, FAQs, routes, and actions.
- [Concise agent summary](https://useglimps.com/llms.txt) — short product and URL index.
- [Extended agent summary](https://useglimps.com/llms-full.txt) — positioning, capabilities, pricing, and retrieval guidance.
- [API catalog](https://useglimps.com/.well-known/api-catalog) — RFC 9264-style discovery links.
- [Agent Skills index](https://useglimps.com/.well-known/agent-skills/index.json) — machine-readable skill discovery.
- [Health endpoint](https://useglimps.com/health.json) — public data surface health.
- [XML sitemap](https://useglimps.com/sitemap.xml) — localized HTML and Markdown page targets.

## Markdown fallbacks

Localized pages with a Markdown twin expose an `index.md` URL. For example:

- [Dutch homepage](https://useglimps.com/nl/index.md)
- [English homepage](https://useglimps.com/en/index.md)
- [Dutch pricing](https://useglimps.com/nl/pricing/index.md)
- [Dutch Exact Online invoice processing](https://useglimps.com/nl/factuurverwerking-exact-online/index.md)

When requesting Markdown through content negotiation, clients should send `Accept: text/markdown`. The production edge must return the Markdown representation and include `Vary: Accept, Accept-Encoding`.

## MCP

The Glimps MCP transport is available at [https://useglimps.com/mcp](https://useglimps.com/mcp). It is a separate authenticated Streamable HTTP service. Clients must use the advertised OAuth resource metadata and request the documented `glimps:read` or `glimps:act` scope. MCP capability changes, including `resources/list`, are maintained in the MCP backend rather than this static frontend repository.

## Product source of truth

Use `agent-data.json` first for product facts. Use the Markdown page twins for page-specific context. Use HTML pages only when those machine-readable sources do not contain enough detail.