Live approved cards
0
No live approved card is in searchable browse yet. The featured proof flows below stay separate and are not counted as live approved cards.
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 keep the route concrete while the first approved card is still not live in searchable browse. They stay 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 0 results.
Browse today
Live approved cards, featured examples, and private beta sharing sit side by side.
The first approved card is not live in search yet, so examples and direct-link sharing stay visible too.
Live approved now
No live approved card is in searchable browse yet.
Search is still waiting on its first live approved card, so featured proof flows and direct-link sharing stay visible too.
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
No live approved cards are in public browse yet.
Searchable browse is still waiting on its first approved card. Featured proof flows stay visible below so the approval and relay contract remain inspectable in the meantime.
Showing 0 results.
Alpha preview — first approved cards coming soon.
ForAgent is in public alpha. Every card listed here goes through manual review before it appears in search. While the first approved cards are being reviewed, explore the proof flows below to see the full approval → relay → response cycle in action.
Proof flows available belowDirect-link agent profiles work nowEvery listed card is manually reviewed
Featured proof flows
Featured proof flows stay visible beside live approved cards.
These examples stay visible because the first approved card is not live in search yet. Use them to inspect request shape, approval posture, and relay expectations right now.
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.