ResolvedAgent Feeds files
Feed files paused during a library update
to 12:19 AM, 14 minutes
- 12:05 AMInvestigating. Feed files answer 503 while the library update runs.
- 12:19 AMResolved. The update finished and feed files answer again.
Live readings from the service, taken each time you open this page.
All times Eastern (EDT, UTC-4).
Working
Every check passed at 8:20 PM on October 25, 2026. Four need a Baltor key and show example values.
MCP connectionbaltor.ai/mcp
Working
Library searchintelligence_search
Working
Downloadsprovisioning_read
Working
Keys can be checked
Working
Sign-up and sign-inEmail first
Working
Checkout and billing portalStripe
Working
OAuth connectionsApprove in the browser
Working
Agent Feeds filesJSON Feed, RSS, Markdown
WorkingRead live
Overnight worker connectionbaltor.ai/workers/mcp
WorkingService record
baltor.aiHome, pricing and account
WorkingRead live
baltor.ai/docsDocumentation
WorkingRead live
baltor.ai/blogEngineering blog
WorkingRead live
baltor.ai/showcaseShowcase
WorkingRead live
baltor.ai/deckDeck
WorkingRead live
Each incident keeps its updates, newest last, in Eastern time. These three show the format the live page uses.
ResolvedAgent Feeds files
to 12:19 AM, 14 minutes
ResolvedSign-up and sign-in
to 10:25 AM, 45 minutes
ResolvedDownloads
to 3:47 PM, 35 minutes
One email when an incident opens, one for each update and one when it is resolved.
Read it from a script or an agent. The same readings answer as JSON.
This service, as it answers right now: search, downloads, accounts and payment, feeds, overnight work and the pages of baltor.ai. Your model provider, your agent and your own machine report their own status.
When this page says the service works and your agent still fails, the troubleshooting page explains each answer the service gives.