Skip to content

docs: enterprise leads, env scoping, Go SDK, vault, capabilities, and resource-list docs#34

Merged
mastermanas805 merged 8 commits into
mainfrom
feat/llms-enterprise-and-sdk-updates
Jul 5, 2026
Merged

docs: enterprise leads, env scoping, Go SDK, vault, capabilities, and resource-list docs#34
mastermanas805 merged 8 commits into
mainfrom
feat/llms-enterprise-and-sdk-updates

Conversation

@mastermanas805

Copy link
Copy Markdown
Member

Summary

  • Document POST /api/v1/leads enterprise contact endpoint (field validation, error codes, MCP tool pointer)
  • Document env parameter for all provisioning endpoints (default: development)
  • Add Go SDK section with typed examples for provision/deploy/operate/leads
  • Expand get_capabilities / GET /api/v1/capabilities with REST path and response shape
  • Document vault REST paths (PUT + /rotate) and vault://env/KEY injection pattern
  • Add 402 error code and agent_action upgrade link for resource-count cap hits
  • Document GET /api/v1/resources list endpoint with service/env filter params

Test plan

  • CI passes (typos + link check)
  • llms.txt renders correctly (no broken formatting)

🤖 Generated with Claude Code

mastermanas805 and others added 8 commits June 23, 2026 11:00
Agents omitting env were silently landing resources in 'development'
without knowing it. Surface the default and semantics explicitly so an
agent building a production stack passes env='production' rather than
leaving the dashboard column empty.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Go agents were using curl in generated code instead of the typed SDK.
Surfacing the SDK in llms.txt gives LLMs an ergonomic first choice:
typed structs, INSTANT_TOKEN resolution, *APIError with AgentAction.
Includes CreateLead since agents hitting Enterprise limits need a
type-safe way to escalate to sales without hand-rolling JSON.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…se shape

Agents using the MCP tool knew to call get_capabilities before
provisioning, but agents using curl had no documented REST equivalent.
Adding the GET /api/v1/capabilities path + response shape means
non-MCP agents can also avoid 402s by checking limits first.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Agents writing secrets without the MCP tool had no documented REST
path. Adding PUT + rotate paths and explaining how vault:// URIs are
resolved at pod startup prevents agents from hard-coding secrets in
env_vars instead of using the encrypted vault surface.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
docs/claim.md said claiming moves resources to 'hobby by default ($9/mo)',
contradicting policy + home.md/pricing.md/llms.txt: claiming gives a Free-tier
account (24h TTL, same limits as anonymous), NOT an automatic paid plan.
Resources keep expiring at 24h until the user upgrades. Reframed to the
canonical pricing.md/llms.txt copy + the no-trial/pay-from-day-one policy.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Surface the new leads endpoint in llms.txt so agents know to call it
when a user needs capacity beyond Pro (dedicated infra, SAML, compliance)
rather than asking the agent to invent a path. Includes field validation
rules (email required, name/company/use_case lengths, error codes).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Agents hitting the resource-count cap were retrying indefinitely or
showing generic errors. Documenting the exact error code and that
agent_action carries an upgrade link gives agents a clear recovery path.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Agents starting a new session had no way to discover existing resources
without reprovisioning. Documenting the list endpoint with its filter
params prevents duplicate provision calls and keeps agent state coherent
across conversation turns.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@mastermanas805
mastermanas805 enabled auto-merge (rebase) July 5, 2026 13:39
@mastermanas805
mastermanas805 merged commit 9303a04 into main Jul 5, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant