This Build 2 slice accepts provider telemetry through a service-scoped ingest key and rolls it up hourly for revenue, conversion, latency, and agent-activity views.
Browserbase · Service view
Browserbase
Headless browser sessions, web search, and page fetching for AI agents.
Stale
45/100 · Stale
At a glance
Service healthStale · 45/100
Cheapest price now$0.01
Best value now59/100
Endpoints6
Open incidents2
Observed price samples1,498
Manifest source
Manifest URLNot configured
Last syncNever
Last sync errorNone
Manifest refresh updates matching endpoints, adds newly declared ones, and then queues reverification. Missing endpoints are left in place for safety instead of being auto-deleted.
Health over time
Hourly service-level snapshots are appended whenever endpoint/service health recomputes.
Latest45/100Stale
High69best recorded bucket
Low45worst recorded bucket
Buckets7hourly snapshots
Price and value over time
Cheapest observed service price 0.01 USD is holding steady across 7 recorded bucket(s).
Cheapest now$0.012 priced endpoint(s)
Average now$0.01latest service average
Best value now59/100avg 59/100
Cheapest change$00%
Value directionTrending downbest -26
Fingerprints141,498 observed sample(s)
Provider analytics
Hourly Build 2 telemetry from provider-installed middleware. This is where revenue, conversion, latency, and agent traffic start compounding back into the registry.
Challenges0last 168h
Paid0no conversion yet
Revenue$00 unique agent(s)
Failures0no failure rate yet
Avg latencyNo latency yetno event timestamp yet
Active keys0service-scoped ingest keys
No provider telemetry has been ingested for this service yet.
Top methods
No method-level telemetry yet.
Top intents
No intent-level telemetry yet.
Pipeline notes
Recovery windows
Service freshness gap
Active
2 endpoint(s) in this service have stale monitoring evidence.
Opened
ResolvedNever
Regressions0
Recovery windown/a
Service freshness gap
Recovered
1 endpoint(s) in this service have stale monitoring evidence.
Opened
Resolved
Regressions0
Recovery window0m
Service freshness gap
Recovered
1 endpoint(s) in this service have stale monitoring evidence.
Opened
Resolved
Regressions0
Recovery window0m
Service freshness gap
Recovered
1 endpoint(s) in this service have stale monitoring evidence.
Opened
Resolved
Regressions0
Recovery window0m
Service freshness gap
Recovered
1 endpoint(s) in this service have stale monitoring evidence.
Opened
Resolved
Regressions0
Recovery window0m
Service freshness gap
Recovered
1 endpoint(s) in this service have stale monitoring evidence.
Opened
Resolved
Regressions0
Recovery window0m
Service still relies on declared coverage
Active
4 endpoint(s) in this service still rely mostly on documented metadata instead of runtime proof.
Opened
ResolvedNever
Regressions0
Recovery windown/a
Alert timeline
Service freshness gap
Opened
2 endpoint(s) in this service have stale monitoring evidence.
Service freshness gap
Resolved
1 endpoint(s) in this service have stale monitoring evidence.
Service freshness gap
Opened
2 endpoint(s) in this service have stale monitoring evidence.
Service freshness gap
Resolved
1 endpoint(s) in this service have stale monitoring evidence.
Service freshness gap
Opened
2 endpoint(s) in this service have stale monitoring evidence.
Service freshness gap
Resolved
1 endpoint(s) in this service have stale monitoring evidence.
Service freshness gap
Opened
2 endpoint(s) in this service have stale monitoring evidence.
Service freshness gap
Resolved
1 endpoint(s) in this service have stale monitoring evidence.
Service freshness gap
Opened
1 endpoint(s) in this service have stale monitoring evidence.
Service freshness gap
Resolved
1 endpoint(s) in this service have stale monitoring evidence.
Service freshness gap
Opened
1 endpoint(s) in this service have stale monitoring evidence.
Service still relies on declared coverage
Opened
4 endpoint(s) in this service still rely mostly on documented metadata instead of runtime proof.
Active incidents
Service freshness gap
Warning
2 endpoint(s) in this service have stale monitoring evidence.
Service still relies on declared coverage
Info
4 endpoint(s) in this service still rely mostly on documented metadata instead of runtime proof.
Attached endpoints
POST
https://mpp.browserbase.com/browser/session/:id/extend
Endpoint health is mostly based on declared workflow metadata because runtime monitoring is still incomplete.
DELETE
https://mpp.browserbase.com/browser/session/:id
Endpoint health is mostly based on declared workflow metadata because runtime monitoring is still incomplete.
POST
https://mpp.browserbase.com/browser/session/create
Endpoint health is mostly based on declared workflow metadata because runtime monitoring is still incomplete.
GET
https://mpp.browserbase.com/browser/session/:id/status
Endpoint health is mostly based on declared workflow metadata because runtime monitoring is still incomplete.
POST
https://mpp.browserbase.com/search
Endpoint still has usable evidence, but freshness or workflow proof is aging out.
POST
https://mpp.browserbase.com/fetch
Endpoint still has usable evidence, but freshness or workflow proof is aging out.