# Meradomo

> Build apps that run on a user's own computer and reach them from anywhere — through Meradomo.

## Docs

- [Exchange a code or refresh token for an access token](https://developers.meradomo.com/api-reference/connect-oauth/exchange-a-code-or-refresh-token-for-an-access-token.md)
- [Fetch the token-signing public key (PEM)](https://developers.meradomo.com/api-reference/connect-oauth/fetch-the-token-signing-public-key-pem.md)
- [Start the OAuth authorization-code flow (PKCE S256)](https://developers.meradomo.com/api-reference/connect-oauth/start-the-oauth-authorization-code-flow-pkce-s256.md): Redirect the user here. On approval the browser is redirected to redirect_uri with a code and state.
- [API reference](https://developers.meradomo.com/api-reference/introduction.md): The two HTTP surfaces that make up the Meradomo integration API.
- [Agent connection state + published apps](https://developers.meradomo.com/api-reference/publish/agent-connection-state-+-published-apps.md)
- [Poll publish status](https://developers.meradomo.com/api-reference/publish/poll-publish-status.md)
- [Publish a local app](https://developers.meradomo.com/api-reference/publish/publish-a-local-app.md): Request that a locally-running app be made reachable. First call returns 202 pending (awaiting owner approval); once approved, returns 200 live.
- [Stop a live app (keeps approval)](https://developers.meradomo.com/api-reference/publish/stop-a-live-app-keeps-approval.md): Removes the live route but keeps the owner's approval, so a subsequent POST /publish is immediately live.
- [Fridge Notes (Publish)](https://developers.meradomo.com/examples/fridge-notes.md): A runnable sample app that publishes itself through Meradomo and reads visitor identity — no sign-in code.
- [Remote Notes Client (Connect)](https://developers.meradomo.com/examples/remote-notes-client.md): A runnable OAuth 2.0 + PKCE reference client for the Connect with Meradomo flow.
- [Agent API](https://developers.meradomo.com/guides/agent-api.md): The local management API your app uses to publish itself and read visitor identity.
- [Connect with Meradomo (OAuth)](https://developers.meradomo.com/guides/oauth.md): The OAuth 2.0 + PKCE flow that lets your remote client obtain an access token for a Meradomo user.
- [Security model](https://developers.meradomo.com/guides/security-model.md): What your app can trust when it runs behind Meradomo.
- [Build for Meradomo](https://developers.meradomo.com/introduction.md): Make an app that runs on a user's own computer, and let them reach it from anywhere — with verified identity, no sign-in code, and no servers to run.
- [Quickstart](https://developers.meradomo.com/quickstart.md): Publish a sample app through Meradomo and reach it remotely — in about 10 minutes.

## OpenAPI Specs

- [openapi](https://developers.meradomo.com/api-reference/openapi.json)