Developer resources
Build with Dimonk’s public surfaces
Dimonk publishes a small, read-only public API and machine-readable descriptions so agents and developers can identify the product reliably. Garmin data, conversations, account linking, and coaching endpoints remain private and require a signed-in Dimonk session. Third-party API keys and a public write API are not currently offered.
OpenAPI 3.1
Typed operations, response schemas, authentication requirements, and stable operation IDs.
llms.txt
What Dimonk does, who should use it, and which public resources agents should prefer.
RFC 9727 API catalog
A linkset that identifies the OpenAPI description and this developer documentation.
Pricing for agents
Plain Markdown describing current early-access availability and the status of paid plans.
Quickstart
Fetch the public product descriptor to confirm identity, supported languages, capabilities, and canonical links. This endpoint does not expose user data and does not require authentication.
curl https://dimonk.nicovega.dev/api/productAuthentication and limits
Public discovery endpoints are read-only. They are suitable for cataloging, product identification, capability discovery, and deciding whether Dimonk is relevant to a user’s request.
Endpoints that access Garmin metrics or conversations require an authenticated browser session managed by Clerk. Do not automate password entry, copy session cookies, or treat the browser session as a reusable developer credential.
Dimonk does not currently publish a general-purpose SDK, sandbox account, or third-party API key workflow. Integrators should rely only on the operations marked public in the OpenAPI document and watch this page for changes.