# letme.dev service level (slim)

> What we commit to for letme.dev, its API and its MCP tools. 99.9% availability each calendar month as the public status page measures it, a written post-mortem for any outage longer than 15 minutes, and 90 days' notice before a breaking change. letme is free, so there's no money back.

- Full: https://www.anchorterminal.com/sla/index.md (~950 tokens) · this version ~530 tokens · JSON https://www.anchorterminal.com/sla/index.json · canonical https://www.anchorterminal.com/sla/
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-10-20
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

This applies from 20 October 2026. It covers [letme.dev](/letme/), its HTTP API and its MCP server at `https://letme.dev/mcp`.

## What we commit to

- **99.9% availability each calendar month**, in UTC. That's about 43 minutes down in a 30-day month and 44 in a 31-day one.
- **A written post-mortem for any outage longer than 15 minutes.** What broke, when, for how long, why, and what we changed so it doesn't happen the same way again.
- **At least 90 days' notice before a breaking change** to letme's API or its MCP tools. A breaking change is one that makes a request or a tool call that works today fail or mean something else. New fields, new tools and new filters aren't breaking changes and can ship without notice.

letme is free to use, so a month under 99.9% earns no money back.

## How it's measured

The [status page](/status/) probes letme.dev every five minutes, with the same pollers that watch every listing in the directory, and shows uptime by day for the last 31 days and every outage in the last 90.

Down means the same thing here as on /status/.

That rule has a cost you should know about.

## What it can't see yet

The probes run on the same machine as letme.dev.

A day with fewer than nine in ten of a full day's 288 probes says so on /status/, rather than counting as clean.

Probes from a second place, off this machine, are the fix.

## What's excluded

Nothing.

## Where post-mortems and notices go

Post-mortems and notices of breaking changes are published in the [changelog](/changelog/), where deprecations have always been announced at least 90 days ahead.

To tell us letme.dev is down when /status/ doesn't show it, file it on the [public issue tracker](/issues/), where we reply in the open, or use the [contact form](/about/#contact).