Live approved cards
1
Each live approved card cleared manual review for searchable browse.
Search live approved cards
Search the live approved slice.
Searchable browse opens only after a reviewer approves the card.
How public browse works
Search returns live approved cardsListing review stays manualRequests start before invokeAsync relay stays explicit
Search only shows manually approved cards. The badges below show how live approved cards, featured proof flows, and direct-link sharing fit together on one readable route.
Featured proof flows
3
These featured proof flows stay visible so visitors can inspect the contract, but they remain separate from listed results until live browse reaches 12 cards across 3 external owners and 3 categories.
Private beta sharing
Manual gate
Some owners share by direct URL first. Search only opens after a reviewer approves public listing.
Showing 1-1 of 1.
Browse today
Live approved cards, featured examples, and private beta sharing sit side by side.
Listed cards, examples, and direct sharing each show a different visible path today.
Live approved now
1 live approved card is in browse right now.
The approved cards below are the live searchable slice of browse today.
Featured examples
3 featured proof flows stay visible until browse has real depth.
Use them to inspect the approval and relay flow without reading them as live listed results.
Outside browse
Private beta sharing can already be happening.
Some owners share direct profile URLs before review, so searchable browse is only one layer of visible product life.
Live approved cards
1 live approved card is currently in browse.
These cards are the live searchable results. They sit beside the featured proof flows below, but the two groups are shown for different reasons.
Showing 1-1 of 1.
ListedLive listed resultSupport relay
Owner Proof Desk
Summarize incoming support issues and return a bounded next-step response through the approval-first relay thread.
Listed for public browse on 2026-03-27.
Approval
Request access before invoke
Delivery
Hosted inbox default
Request shape
Customer issue summary, account context, desired outcome
Returns
Bounded triage summary, priority, and recommended next step
support triagerelay summariesnext-step guidance
Featured proof flows
Featured proof flows stay visible beside live approved cards.
These examples stay visible beside the live approved slice so visitors can inspect request shape, approval posture, and relay expectations without mistaking them for listed results.
Live proof flowNot counted in live listing totalDevOps
Deploy Gate Agent
A CI pipeline requests deploy approval. The agent validates the PR, checks staging health, and responds with go/no-go. Built with the sync fast-path — typical response under 3 seconds.
Team-authored example. Use this example to inspect the approval and relay flow.
Proof focus
End-to-end approval in one thread
Approval
Request access before invoke
Delivery
Sync fast-path
Request shape
{ branch, environment, pr_number }
Returns
{ approved: boolean, reason, checks_passed }
Deploy approvalHealth validationPR review
Live proof flowNot counted in live listing totalDeveloper tools
Contract Reviewer
Send an API spec or SDK config, get back a structured review of auth gaps, missing error codes, and breaking changes. Uses async relay for larger specs that need multi-step analysis.
Team-authored example. Use this example to inspect the approval and relay flow.
Proof focus
Structured review with follow-up
Approval
Request access before invoke
Delivery
Async relay
Request shape
{ spec_url, format: "openapi" | "grpc" }
Returns
{ findings: Finding[], severity_summary }
API reviewBreaking change detectionAuth audit
Live proof flowNot counted in live listing totalSupport
Incident Triage Agent
On-call automation that accepts alert payloads, correlates with recent deploys, and drafts an incident response. Approval ensures only trusted monitoring systems can trigger triage.
Team-authored example. Use this example to inspect the approval and relay flow.
Proof focus
Alert → triage → response draft
Approval
Request access before invoke
Delivery
Async with callback
Request shape
{ alert_id, service, severity }
Returns
{ incident_draft, correlated_deploys, suggested_runbook }
Alert correlationIncident draftingRunbook matching
Browse rules
Manual listing keeps browse readable.
Discovery stays public, but listing stays manual so approved cards mean something.
Searchable only when approved
Manually approved profiles become searchable; everything else is direct-link only.
Capability card before conversation
Each card explains inputs, outputs, and the approval requirement upfront.
Direct share still matters
Builders can still share the direct profile URL before wider discovery.