specific.dev valid
Specific Docs
Specific enables any coding agent to define infrastructure for the code it writes. Start building locally and deploy to production in minutes.
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-27T10:02:12.905Z. Cached copy · Source on specific.dev
# Specific Docs
> Specific enables any coding agent to define infrastructure for the code it writes. Start building locally and deploy to production in minutes.
## Docs
- [Welcome](https://docs.specific.dev/): Specific enables any coding agent to define infrastructure for the code it writes. This lets you start building locally and deploy to production in minutes.
## Get started
- [Quickstart](https://docs.specific.dev/quickstart): Let your agent set everything up, or go from local dev to deployed yourself in about five minutes.
- [Installation](https://docs.specific.dev/installation): Install the Specific CLI and prepare your project.
- [Coding agents](https://docs.specific.dev/coding-agents): Give your coding agent everything it needs to build and deploy with Specific.
- [Why Specific?](https://docs.specific.dev/why-specific): The case for agent-first infrastructure.
## Guides
- [Services](https://docs.specific.dev/guides/services): Define how your code runs and how it connects to everything else, in development and production.
- [Builds](https://docs.specific.dev/guides/builds): Define how your code is built: managed base environments or custom Dockerfiles.
- [Crons](https://docs.specific.dev/guides/crons): Scheduled jobs with tracked runs, logs, and metrics.
- [Secrets and config](https://docs.specific.dev/guides/secrets-and-config): Parameterize sensitive and environment-specific values without hardcoding them.
- [Postgres](https://docs.specific.dev/guides/postgres): Managed PostgreSQL databases, locally and in production.
- [Reshape migrations](https://docs.specific.dev/guides/reshape): Zero-downtime database schema migrations, managed automatically.
- [Real-time sync](https://docs.specific.dev/guides/sync): Stream Postgres changes to clients over HTTP, powered by Electric.
- [Object storage](https://docs.specific.dev/guides/storage): S3-compatible object storage that works with any S3 client.
- [Redis](https://docs.specific.dev/guides/redis): Managed Redis-compatible caching backed by Valkey: one block in specific.hcl, a local instance during specific dev, and a connection URL your existing Redis client already understands.
- [Volumes](https://docs.specific.dev/guides/volumes): Persistent directories that survive deploys and restarts.
- [Managed Temporal](https://docs.specific.dev/guides/temporal): Managed Temporal workflow engines for durable workflows: a local dev server with specific dev, and an auto-provisioned Temporal Cloud namespace in production.
- [Custom domains](https://docs.specific.dev/guides/domains): Serve your services from domains you own, with automatic TLS.
- [Preview environments](https://docs.specific.dev/guides/previews): Temporary copies of an environment for testing changes with real data.
- [Observability](https://docs.specific.dev/guides/observability): Query your environments' logs and metrics with SQL.
- [Alerts](https://docs.specific.dev/guides/alerts): Default alerts on every service, with email and web
…
Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| encore.dev | Encore | documentation Infrastructure AI agents and MCP +1 | SE | 61 | ✓ | ✓ | |
| suga.app | Suga | documentation Infrastructure Developer tools | US | 51 | ✓ | ✓ | |
| insforge.dev | InsForge | interface Infrastructure AI agents and MCP +1 | US | 50 | ✓ | ||
| spawned.ai | Spawned | documentation Infrastructure AI and machine learning | — | 48 | ✓ | ✓ | |
| dcdeploy.com | DCDeploy Docs | documentation Infrastructure | US | 46 | ✓ | ✓ | |
| simplebackups.com | SimpleBackups | documentation AI and machine learning Infrastructure | US | 56 | ✓ | ✓ | |
| kedge.dev | Kedge | interface Infrastructure Developer tools | US | 50 | ✓ | ✓ | |
| northflank.com | Northflank Documentation | interface Infrastructure DevOps and observability | — | 59 | ✓ |
Machine-readable: GET /v1/resolve?q=specific.dev · GET /v1/domain/specific.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 specific.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 specific.dev:
1. POST https://agentwebmap.com/v1/sites/specific.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://specific.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/specific.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/specific.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.