letmepost.dev valid
letmepost.dev
Open-source social media publishing API. Preflight validation, transparent errors, idempotency, stable platform versions.
- Authority
- 45 reach 0 · trust 5 · quality 25 · freshness 15
- Tier
- listed
- llms.txt
- https://docs.letmepost.dev/llms.txt
- llms-full.txt
- https://docs.letmepost.dev/llms-full.txt
- Sections
- 1
- Links
- 159
- Size
- 29065 bytes
- Country
- — Publisher location unknown; CDN address excluded
- Country evidence
- No published address evidence collected yet
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-27T09:55:58.003Z
- Last checked
- 2026-10-27T09:56:01.775Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-27T09:55:58.007Z. Cached copy · Source on letmepost.dev
# letmepost.dev
> Open-source social media publishing API. Preflight validation, transparent errors, idempotency, stable platform versions.
- [Quickstart](https://docs.letmepost.dev/quickstart.md): Publish your first tweet via curl in 90 seconds.
- [Authentication](https://docs.letmepost.dev/authentication.md): API keys, scoping, and rotation. Bearer tokens, scoped per organization.
- [Idempotency](https://docs.letmepost.dev/idempotency.md): Every write accepts an Idempotency-Key. Retries are safe. No double-posting.
- [Errors](https://docs.letmepost.dev/errors/index.md): The thirteen error codes, the response shape, and what to do about each one.
- [Preflight](https://docs.letmepost.dev/preflight/index.md): Every documented platform constraint is checked locally before we touch the upstream API. Here are all the rules.
- [MCP server](https://docs.letmepost.dev/agents/mcp.md): Use letmepost.dev from Claude Code, Cursor, Claude Desktop, or any MCP-compatible client. 21 tools, autogenerated from the OpenAPI spec.
- [CLI](https://docs.letmepost.dev/agents/cli.md): A command-line client for letmepost.dev. Publish from your terminal or from any agentic tool that can shell out.
- [Accounts](https://docs.letmepost.dev/guides/connect-account.md): Connect, refresh, fan-out. The OAuth lifecycle for each platform.
- [Publish a post](https://docs.letmepost.dev/guides/publish-post.md): From key to published — the synchronous path, the scheduled path, and what to subscribe to in between.
- [Scheduled posts](https://docs.letmepost.dev/guides/schedule-post.md): Pass scheduledAt to queue a batch for the future. 202 instead of 200, queued status per target, post.queued webhook per target.
- [Media](https://docs.letmepost.dev/guides/upload-media.md): Three ways to attach media. Why mediaId is the production answer.
- [Quick start](https://docs.letmepost.dev/self-host/quick-start.md): Get the API, worker, and dashboard running locally against a Postgres + Redis you control.
- [Environment variables](https://docs.letmepost.dev/self-host/environment.md): Every variable the API reads, what defaults to what, and which ones are required to boot.
- [Platform credentials](https://docs.letmepost.dev/self-host/platform-credentials.md): Register the developer apps that let your self-hosted instance talk to each social network.
- [Deploying](https://docs.letmepost.dev/self-host/deploying.md): Two-service split, managed Postgres + Redis, custom domain, zero-downtime migrations.
- [Troubleshooting](https://docs.letmepost.dev/self-host/troubleshooting.md): Common boot failures, what they mean, and how to fix them.
- [Migrate from Postiz](https://docs.letmepost.dev/guides/migrate-from-postiz.md): Map your existing Postiz publishing flow to letmepost.dev.
- [Migrate from Ayrshare](https://docs.letmepost.dev/guides/migrate-from-ayrshare.md): Map your existing Ayrshare publishing flow to letmepost.dev.
- [Migrate from Buffer](https://docs.letmepost.dev/guides/migrate-from-buffer.md
…Machine-readable: GET /v1/resolve?q=letmepost.dev · GET /v1/domain/letmepost.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage letmepost.dev, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for letmepost.dev:
1. POST https://agentwebmap.com/v1/sites/letmepost.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://letmepost.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/letmepost.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/letmepost.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.