# Composio vs Browserbase

Composio is open source and Browserbase is not, so the question is whether you want source access and the option to fork, or would rather have a vendor accountable for it.

| | Composio | Browserbase |
| --- | --- | --- |
| Licence | Open source | Proprietary |
| Pricing | freemium | freemium |
| Self-hostable | No | No |
| Languages | Python, TypeScript | TypeScript, Python |
| Install | pip install composio | — |
| Keys required | COMPOSIO_API_KEY | BROWSERBASE_API_KEY, BROWSERBASE_PROJECT_ID |

## Full pages

- https://newagent.build/c/composio
- https://newagent.build/c/browserbase

## Machine interfaces

- `GET https://newagent.build/api/registry` — every component as JSON
- `GET https://newagent.build/api/vendors` — vendors, with the repo and releases feed to watch
- `GET https://newagent.build/api/advise?q=<plain english>` — recommended stack for a description
- `GET https://newagent.build/api/stack?<layer>=<id>&format=sh|json|md|yml|agents|env` — a stack as files
- `GET https://newagent.build/llms.txt` — the whole registry in one fetch

Any page here also returns markdown if you send `Accept: text/markdown`.