Rank #3 of 5 in API platforms
Access
Showcase


Verified integrations
Connections to other tracked products — hover a chip for the verbatim evidence quote behind it.
By theme — the product's score on each story themeBy theme
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Ci scripting — stories about ci scripting in this arenaCi scriptingevidence →
Stories about ci scripting in this arena
Collaboration — working as a team — sharing, comments, roles, simultaneous editingCollaborationevidence →
Working as a team — sharing, comments, roles, simultaneous editing
Collections workspaces — stories about collections workspaces in this arenaCollections workspacesevidence →
Stories about collections workspaces in this arena
Environments secrets — stories about environments secrets in this arenaEnvironments secretsevidence →
Stories about environments secrets in this arena
Gateway traffic — stories about gateway traffic in this arenaGateway trafficevidence →
Stories about gateway traffic in this arena
n/a
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Spec design — stories about spec design in this arenaSpec designevidence →
Stories about spec design in this arena
Testing mocking — stories about testing mocking in this arenaTesting mockingevidence →
Stories about testing mocking in this arena
Story verdicts — every judged story with its evidenceStory verdicts
What’s free: 3 free · 0 paid · 0 enterprise · 28 not stated in evidence
Follow the green: where the map greys out is where Bruno stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
~5/10
unlocks → Official SDKs · Scoped API keys · MCP server · Machine-readable spec · Versioning policy
Subscribe to events via webhooks
n/an/a
Build against official SDKs
—–
Issue scoped/least-privilege API credentials for an agent
—0/10
Connect an agent via an official MCP server
—0/10
Download a machine-readable API spec (OpenAPI or equivalent)
—0/10
Rely on versioned APIs with a documented deprecation policy
—–
Test against a sandbox environment without touching production data
~5/10
Explore an interactive API reference with runnable examples
~4/10
Docs for agents
Point an agent at llms.txt or agent-oriented docs
✓8/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
~6/10
unlocks → MCP client
Operate the product with natural-language commands
~6/10
Plug MCP servers into this product so it can use their tools
—–
Get AI-generated insights and suggestions from my data inside the product
~7/10
Set up automations that run autonomously in the background
~4/10
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Ci scripting — stories about ci scripting in this arenaCi scripting
Stories about ci scripting in this arena
Collaboration — working as a team — sharing, comments, roles, simultaneous editingCollaboration
Working as a team — sharing, comments, roles, simultaneous editing
Collections workspaces — stories about collections workspaces in this arenaCollections workspaces
Stories about collections workspaces in this arena
Environments secrets — stories about environments secrets in this arenaEnvironments secrets
Stories about environments secrets in this arena
Gateway traffic — stories about gateway traffic in this arenaGateway traffic
Stories about gateway traffic in this arena
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Spec design — stories about spec design in this arenaSpec design
Stories about spec design in this arena
Testing mocking — stories about testing mocking in this arenaTesting mocking
Stories about testing mocking in this arena
Sorted by importance (agentic first) (high → low) · 57/57 stories · click a row’s chevron for the rationale and evidence
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | partial | 6/10 | Cclaimed | |
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | partial | 5/10 | Tprobed | |
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | 0/10 | ||
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | untested | none yet | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 9/10 | Tprobed | |
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 7/10 | Cclaimed | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 7/10 | Tprobed | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Cclaimed | |
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 4/10 | Tprobed | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 4/10 | Cclaimed | |
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | n/a | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | partial | 5/10 | Cclaimed | |
Store collections as plain text files in my repo and version them with git C Collections | developer | Collections workspaces — stories about collections workspaces in this arenaCollections workspaces | 3 | fullfree | 10/10 | Xcommunity | |
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | full | 9/10 | Xcommunity | |
Run an entire collection as an automated test suite with a pass/fail report C Testing | developer | Testing mocking — stories about testing mocking in this arenaTesting mocking | 3 | full | 9/10 | Tprobed | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | full | 8/10 | Xcommunity | |
Organize API requests into collections and folders and rerun them anytime C Collections | developer | Collections workspaces — stories about collections workspaces in this arenaCollections workspaces | 3 | full | 8/10 | Xcommunity | |
Run my API test collections in CI with a CLI and fail the build on regressions C Ci | developer | Ci scripting — stories about ci scripting in this arenaCi scripting | 3 | full | 8/10 | Tprobed | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | full | 8/10 | Xcommunity | |
Write test assertions against response status, body, and headers C Testing | developer | Testing mocking — stories about testing mocking in this arenaTesting mocking | 3 | full | 7/10 | Cclaimed | |
Switch requests between dev, staging, and prod using environment variable sets C Environments | developer | Environments secrets — stories about environments secrets in this arenaEnvironments secrets | 3 | partial | 6/10 | Cclaimed | |
Share collections with my team in a synced shared workspace C Team workspaces | developer | Collaboration — working as a team — sharing, comments, roles, simultaneous editingCollaboration | 3 | partialfree | 5/10 | Xcommunity | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | partial | 4/10 | Cclaimed | |
Spin up a mock server from saved examples or a spec so consumers can build before the API exists C Mocking | developer | Testing mocking — stories about testing mocking in this arenaTesting mocking | 3 | partial | 3/10 | Cclaimed | |
Enforce authentication (API keys, OAuth2, JWT, mTLS) on upstream APIs via gateway plugins or policies C Traffic management | platform-engineer | Gateway traffic — stories about gateway traffic in this arenaGateway traffic | 3 | n/a | untested | none yet | |
Enforce rate limits on API traffic per consumer or route C Traffic management | platform-engineer | Gateway traffic — stories about gateway traffic in this arenaGateway traffic | 3 | n/a | untested | none yet | |
Import an OpenAPI spec to generate requests and collections C Spec import export | developer | Spec design — stories about spec design in this arenaSpec design | 3 | none | untested | none yet | |
Lint API specs against configurable style and governance rules C Governance | platform-engineer | Spec design — stories about spec design in this arenaSpec design | 3 | n/a | untested | none yet | |
Work fully offline in a local workspace without a cloud account G Offline | developer | Collections workspaces — stories about collections workspaces in this arenaCollections workspaces | 2 | full | 9/10 | Xcommunity | |
Keep credentials out of shared files with masked secrets or an external vault integration C Secrets | platform-engineer | Environments secrets — stories about environments secrets in this arenaEnvironments secrets | 2 | full | 8/10 | Cclaimed | |
Script pre-request and post-response logic to chain requests and massage data C Scripting | developer | Ci scripting — stories about ci scripting in this arenaCi scripting | 2 | full | 8/10 | Cclaimed | |
Have AI generate test cases or assertions for an endpoint from its spec or responses C Ai assist | ai-native user | Testing mocking — stories about testing mocking in this arenaTesting mocking | 2 | partial | 7/10 | Cclaimed | |
Import and export collections in portable formats to move between tools C Collections | developer | Collections workspaces — stories about collections workspaces in this arenaCollections workspaces | 2 | partial | 7/10 | Cclaimed | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | full | 7/10 | Tprobed | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | partial | 6/10 | Cclaimed | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 6/10 | Tprobed | |
Generate and publish API documentation from my collections or specs C Docs generation | developer | Spec design — stories about spec design in this arenaSpec design | 2 | partial | 6/10 | Cclaimed | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | partial | 6/10 | Cclaimed | |
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | partial | 5/10 | Cclaimed | |
Publish an internal catalog or portal where teams discover and consume our APIs C Api catalog | platform-engineer | Collaboration — working as a team — sharing, comments, roles, simultaneous editingCollaboration | 2 | partial | 4/10 | Cclaimed | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 4/10 | Cclaimed | |
Validate live responses against the API contract to catch drift C Contract testing | platform-engineer | Testing mocking — stories about testing mocking in this arenaTesting mocking | 2 | partial | 4/10 | Cclaimed | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partial | 3/10 | Cclaimed | |
Design an API spec-first and export it as OpenAPI C Spec import export | developer | Spec design — stories about spec design in this arenaSpec design | 2 | none | 0/10 | ||
Schedule collection runs as monitors that alert me when an API breaks C Monitors | developer | Ci scripting — stories about ci scripting in this arenaCi scripting | 2 | none | 0/10 | ||
Send GraphQL, gRPC, WebSocket, and SSE requests, not just REST C Protocols | developer | Collections workspaces — stories about collections workspaces in this arenaCollections workspaces | 2 | none | 0/10 | ||
Control who can view or edit APIs and collections with roles and permissions G Access control | platform-engineer | Collaboration — working as a team — sharing, comments, roles, simultaneous editingCollaboration | 2 | none | untested | none yet | |
Manage API infrastructure as declarative config and sync it from CI (GitOps/APIOps) C Gateway ops | platform-engineer | Gateway traffic — stories about gateway traffic in this arenaGateway traffic | 2 | n/a | untested | none yet | |
Monitor API traffic with metrics, logging, and tracing integrations C Monitoring | platform-engineer | Gateway traffic — stories about gateway traffic in this arenaGateway traffic | 2 | n/a | untested | none yet | |
Proxy and govern LLM/MCP traffic (token limits, prompt guards, provider routing) through the platform C Ai gateway | ai-native user | Gateway traffic — stories about gateway traffic in this arenaGateway traffic | 2 | n/a | untested | none yet | |
Route, load-balance, and transform requests between consumers and upstream services C Traffic management | platform-engineer | Gateway traffic — stories about gateway traffic in this arenaGateway traffic | 2 | n/a | untested | none yet | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | fullfree | 7/10 | Xcommunity |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 33 stories with headroom
What would move Bruno’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agenticness — how well agents can access and operate the productPlug MCP servers into this product so it can use their tools
nonemoves agent-readyimpact 45
Bruno's docs describe AI features (BYOK script generation, AI chat sidebar) but no evidence anywhere mentions MCP server support or plugging in MCP tools for Bruno to use.
Agenticness — how well agents can access and operate the productConnect an agent via an official MCP server
nonemoves agent-readyimpact 45
Bruno is an API client/CLI product where an official MCP server is a plausible feature (e.g., for AI agents to run collections), but no evidence pack item mentions an MCP server, MCP protocol, or agent-connection endpoint — only AI-assisted scripting/chat features (BYOK) are documented, which is a different capability.
Spec design — stories about spec design in this arenaImport an OpenAPI spec to generate requests and collections
nonemoves PA Scoreimpact 30
The evidence pack documents Postman collection import (bruno-docs-24, bruno-docs-25, bruno-docs-7) but contains no mention of importing OpenAPI/Swagger specs to generate requests or collections.
Agenticness — how well agents can access and operate the productIssue scoped/least-privilege API credentials for an agent
nonemoves agent-readyimpact 30
Missing: any credential-issuance or scoping mechanism aimed at agents, documentation of granular permission scopes, or evidence of restricting an agent's API access via generated tokens.
Agenticness — how well agents can access and operate the productBuild against official SDKs
nonemoves agent-readyimpact 30
Evidence shows Bruno offers a CLI (bru-cli), Docker images, and a Bru markup format, but no official SDKs (e.g., client libraries in Python/JS/Go) for programmatic integration are documented anywhere in the pack.
Agenticness — how well agents can access and operate the productDownload a machine-readable API spec (OpenAPI or equivalent)
nonemoves API qualityimpact 30
Missing: any OpenAPI/Swagger JSON or equivalent structured spec, first-party docs describing one, and community confirmation of its existence.
Agenticness — how well agents can access and operate the productRely on versioned APIs with a documented deprecation policy
nonemoves API qualityimpact 30
Evidence shows Bruno ships versioned releases/changelogs (e.g., CLI v4.1.0, release notes) but nothing documents an explicit API/CLI deprecation policy or versioning guarantees that an AI-native user could rely on.
Agenticness — how well agents can access and operate the productDrive the product through a documented public API
partialq5/10moves agent-readyimpact 22.5
Missing: a documented HTTP/REST API or SDK beyond the CLI, official OpenAPI/swagger spec, and evidence of programmatic access outside the CLI wrapper.
Showing the top 8 of 33 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map13 surfaces · 38 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
GitHub README27 stories
- Run the product headlessly / in CI for automation
- Use an official CLI
- Drive the product through a documented public API
- Set up automations that run autonomously in the background
- Test against a sandbox environment without touching production data
- Perform bulk operations across many items at once
- Schedule recurring jobs or workflows
- Version, review, and roll back my automations
- Run my API test collections in CI with a CLI and fail the build on regressions
- Publish an internal catalog or portal where teams discover and consume our APIs
- Share collections with my team in a synced shared workspace
- Store collections as plain text files in my repo and version them with git
- Import and export collections in portable formats to move between tools
- Organize API requests into collections and folders and rerun them anytime
- Work fully offline in a local workspace without a cloud account
- Switch requests between dev, staging, and prod using environment variable sets
- Keep credentials out of shared files with masked secrets or an external vault integration
- Do everything through the API that I can do in the UI
- Export all of my data in open formats and leave
- Read the product's source under an open license
- Self-host the core product
- Choose where my data is stored (region/residency)
- Prevent my data from being used to train AI models
- Control data retention and deletion
- Opt out of telemetry and usage tracking
- Generate and publish API documentation from my collections or specs
- Run an entire collection as an automated test suite with a pass/fail report
Bru CLI docs13 stories
- Run the product headlessly / in CI for automation
- Use an official CLI
- Drive the product through a documented public API
- Set up automations that run autonomously in the background
- Perform bulk operations across many items at once
- Define rules that trigger actions automatically on events
- Schedule recurring jobs or workflows
- Run my API test collections in CI with a CLI and fail the build on regressions
- Organize API requests into collections and folders and rerun them anytime
- Do everything through the API that I can do in the UI
- Validate live responses against the API contract to catch drift
- Run an entire collection as an automated test suite with a pass/fail report
- Write test assertions against response status, body, and headers
API client docs12 stories
- Perform bulk operations across many items at once
- Define rules that trigger actions automatically on events
- Version, review, and roll back my automations
- Script pre-request and post-response logic to chain requests and massage data
- Store collections as plain text files in my repo and version them with git
- Import and export collections in portable formats to move between tools
- Organize API requests into collections and folders and rerun them anytime
- Keep credentials out of shared files with masked secrets or an external vault integration
- Export all of my data in open formats and leave
- Validate live responses against the API contract to catch drift
- Run an entire collection as an automated test suite with a pass/fail report
- Write test assertions against response status, body, and headers
usebruno.com12 stories
- Test against a sandbox environment without touching production data
- Publish an internal catalog or portal where teams discover and consume our APIs
- Share collections with my team in a synced shared workspace
- Store collections as plain text files in my repo and version them with git
- Import and export collections in portable formats to move between tools
- Work fully offline in a local workspace without a cloud account
- Export all of my data in open formats and leave
- Self-host the core product
- Choose where my data is stored (region/residency)
- Prevent my data from being used to train AI models
- Control data retention and deletion
- Opt out of telemetry and usage tracking
Hacker News8 stories
- Version, review, and roll back my automations
- Share collections with my team in a synced shared workspace
- Store collections as plain text files in my repo and version them with git
- Organize API requests into collections and folders and rerun them anytime
- Work fully offline in a local workspace without a cloud account
- Export all of my data in open formats and leave
- Self-host the core product
- Prevent my data from being used to train AI models
AI docs7 stories
- Get AI-generated insights and suggestions from my data inside the product
- Set up automations that run autonomously in the background
- Delegate tasks to a built-in AI assistant inside the product
- Operate the product with natural-language commands
- Prevent my data from being used to train AI models
- Control data retention and deletion
- Have AI generate test cases or assertions for an endpoint from its spec or responses
docs.usebruno.com5 stories
- Explore an interactive API reference with runnable examples
- Test against a sandbox environment without touching production data
- Publish an internal catalog or portal where teams discover and consume our APIs
- Generate and publish API documentation from my collections or specs
- Spin up a mock server from saved examples or a spec so consumers can build before the API exists
Git integration docs5 stories
- Explore an interactive API reference with runnable examples
- Version, review, and roll back my automations
- Publish an internal catalog or portal where teams discover and consume our APIs
- Share collections with my team in a synced shared workspace
- Store collections as plain text files in my repo and version them with git
OpenAPI spec3 stories
Apps docs3 stories
llms.txt2 stories
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
8 of 13 testable claims verified · 0 contradicted → integrity 62/100
20 distinct capability claims found in Bruno’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
8
Verified
5
Unverified
0
Contradicted
25
Undersold
Verified (15)
“CLI can run API collections directly from the command line”
Run my API test collections in CI with a CLI and fail the build on regressionsfullproof ↗
“CLI can run API collections directly from the command line”
“Generates test reports in JSON, JUnit, and HTML formats for analysis and sharing”
Run an entire collection as an automated test suite with a pass/fail reportfullproof ↗
“Integrates with CI/CD pipelines for automated testing and validation”
Run my API test collections in CI with a CLI and fail the build on regressionsfullproof ↗
“Integrates with CI/CD pipelines for automated testing and validation”
Run the product headlessly / in CI for automationfullproof ↗
“Enables native collaboration through version control systems like Git since collections are stored as files”
Store collections as plain text files in my repo and version them with gitfullproof ↗
“Built-in Git UI provides init, diff viewing, update checks, pull, and clone directly in the app”
Store collections as plain text files in my repo and version them with gitfullproof ↗
“Works with no cloud sync or account required, fully local”
Work fully offline in a local workspace without a cloud accountfullproof ↗
“Has zero visibility into user requests and does not train AI models on user data”
Prevent my data from being used to train AI modelsfullproof ↗
“Stores collections directly as files in a folder on the local filesystem”
Work fully offline in a local workspace without a cloud accountfullproof ↗
“Stores collections directly as files in a folder on the local filesystem”
Store collections as plain text files in my repo and version them with gitfullproof ↗
“Requests and collections can be edited without leaving your code editor”
Work fully offline in a local workspace without a cloud accountfullproof ↗
“Official Docker images let you run the CLI in CI/CD or locally without installing Node.js/npm”
Run my API test collections in CI with a CLI and fail the build on regressionsfullproof ↗
“Official Docker images let you run the CLI in CI/CD or locally without installing Node.js/npm”
Run the product headlessly / in CI for automationfullproof ↗
“Can open multiple collections at once from a monorepo”
Organize API requests into collections and folders and rerun them anytimefullproof ↗
Unverified (8)
“Can serve mock API responses while building requests”
Spin up a mock server from saved examples or a spec so consumers can build before the API existspartialproof ↗
“Preserves scripts when importing/exporting Postman collections”
Import and export collections in portable formats to move between toolspartialproof ↗
“CLI flag lets you override global environment variables at runtime”
Switch requests between dev, staging, and prod using environment variable setspartialproof ↗
“Rich text editor for writing collection documentation”
Generate and publish API documentation from my collections or specspartialproof ↗
“Environment selector dropdown supports search filtering”
Switch requests between dev, staging, and prod using environment variable setspartialproof ↗
“Supports drag-and-drop and alphabetical sorting for variables”
Switch requests between dev, staging, and prod using environment variable setspartialproof ↗
“Supports GCP Secret Manager integration for secrets”
Keep credentials out of shared files with masked secrets or an external vault integrationfullproof ↗
“Docs written alongside collections can be published as shareable HTML”
Generate and publish API documentation from my collections or specspartialproof ↗
Undersold (25)
Point an agent at llms.txt or agent-oriented docsfullproof ↗
Drive the product through a documented public APIpartialproof ↗
Get AI-generated insights and suggestions from my data inside the productpartialproof ↗
Set up automations that run autonomously in the backgroundpartialproof ↗
Delegate tasks to a built-in AI assistant inside the productpartialproof ↗
Operate the product with natural-language commandspartialproof ↗
Explore an interactive API reference with runnable examplespartialproof ↗
Test against a sandbox environment without touching production datapartialproof ↗
Perform bulk operations across many items at oncefullproof ↗
Define rules that trigger actions automatically on eventspartialproof ↗
Script pre-request and post-response logic to chain requests and massage datafullproof ↗
Publish an internal catalog or portal where teams discover and consume our APIspartialproof ↗
Share collections with my team in a synced shared workspacepartialproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
Read the product's source under an open licensepartialproof ↗
Choose where my data is stored (region/residency)partialproof ↗
Have AI generate test cases or assertions for an endpoint from its spec or responsespartialproof ↗
Validate live responses against the API contract to catch driftpartialproof ↗
Write test assertions against response status, body, and headersfullproof ↗
Claims outside our story set (1)
Real capability claims found in Bruno’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“Supports global client certificates with per-cert disabling”
source ↗
Business model
Open-source (MIT) desktop client and CLI are free; paid Pro and Ultimate per-user plans add premium collaboration and team features on top.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
Agent surface uptime llms.txt 100% (30d, checked every 6h since Sep 8 '26)
