acai.sh valid
Acai.sh
A toolkit for spec-driven development.
- Authority
- 45 reach 0 · trust 5 · quality 25 · freshness 15
- Tier
- listed
- llms.txt
- https://acai.sh/llms.txt
- llms-full.txt
- https://acai.sh/llms-full.txt
- Sections
- 3
- Links
- 18
- Size
- 3306 bytes
- Country
- United States Hosting inference
- Hosting country
- United States Hosting inference
- Country evidence
- No published address evidence collected yet
- Categories
- Developer tools
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-27T13:26:08.566Z
- Last checked
- 2026-10-27T13:26:10.122Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-27T13:26:08.571Z. Cached copy · Source on acai.sh
# Acai.sh
> A toolkit for spec-driven development.
## Docs
- [Acai.sh](https://acai.sh/index.md): A toolkit for spec-driven software development. Stop writing prompts, start writing specs. Ship better quality software and minimize slop.
- [Quickstart Tutorial](https://acai.sh/quickstart.md): Write your first feature spec and push it to the Acai.sh dashboard. Equip your LLM agents with the `acai` CLI and teach them to follow a spec-first workflow.
- [Acai.sh CLI](https://acai.sh/cli.md): Overview of the Acai.sh Command Line Interface. The CLI facilitates spec-driven development for humans, AI agents, and CI/CD automations.
- [Acai JSON API](https://acai.sh/api.md): Overview of the Acai API and how to access it.
- [Acai Dashboard](https://acai.sh/dashboard.md): A shared view of your team's specs, implementation status, and requirement coverage.
- [Spec-driven Development](https://acai.sh/spec-driven-development.md): Introduction to `feature.yaml` specs, and best practices for spec-first software development.
- [Agent Recipes](https://acai.sh/agents.md): Make the most of acai.sh and agentic development by leveraging LLM skills and roles
- [feature.yaml Specification](https://acai.sh/feature-yaml.md): This is the formal specification for the feature.yaml document format (written as a compliant feature.yaml!)
- [Read canonical feature context](https://acai.sh/api-reference/actions/read-canonical-feature-context.md): Return the complete context for one feature in one implementation.
- [Write feature states](https://acai.sh/api-reference/actions/write-feature-states.md): Record implementation-specific progress for one feature in one implementation. State writes do not change requirement text or code refs; they only capture how this implementation currently evaluates each requirement, for example assigned, blocked, completed, or accepted. On first write, local state…
- [List implementation features](https://acai.sh/api-reference/actions/list-implementation-features.md): Return a summary list of Features that are visible to a given Implementation. These features may be defined in specs that were pushed directly to that Implementation, or inherited from a parent Implementation. The response is a summary list of features, containing some metadata and a summary of code…
- [List implementations](https://acai.sh/api-reference/actions/list-implementations.md): Discover which Implementations exist for a Product. Filter by Repo + Branch name, and by Feature name. This is the orientation endpoint: when you know the current repo and branch, and need to identify the relevant Implementations that track it.
- [Push from branch](https://acai.sh/api-reference/actions/push-from-branch.md): Sync data from your current git branch to the server. - Upload specs (feature.yaml files) and the requirements and metadata defined in them. - Upload code references (ACID tags) found in source code, and their file paths.
- [Blog](https://acai.sh/blog/index.md): Experiments in
…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 |
|---|---|---|---|---|---|---|---|
| agentskills.io | Agent Skills | documentation AI agents and MCP Documentation and reference | US | 55 | ✓ | ✓ | |
| myspec.dev | MySpec (myspec.dev) - Spec-Driven Development Platform & MCP Server | interface AI agents and MCP Developer tools | — | 45 | ✓ | ✓ | |
| contextqa.com | ContextQA | documentation AI agents and MCP Developer tools | — | 52 | ✓ | ✓ | |
| scorecard.io | Scorecard | documentation AI and machine learning DevOps and observability +1 | US | 46 | ✓ | ||
| openspec.dev | Documentation | documentation Developer tools Documentation and reference | — | 49 | ✓ | ✓ | |
| qa.tech | QA.tech | interface AI agents and MCP Developer tools | US | 53 | ✓ | ||
| foomakers.com | pair | documentation Developer tools AI agents and MCP | US | 48 | ✓ | ✓ | |
| teammately.ai | Teammately Docs | interface AI agents and MCP Documentation and reference | — | 50 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=acai.sh · GET /v1/domain/acai.sh · 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 acai.sh, 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 acai.sh:
1. POST https://agentwebmap.com/v1/sites/acai.sh/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://acai.sh/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/acai.sh/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/acai.sh).
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.