osFoundry / Platform
Data sources
Sync from Stripe, Postgres, Mixpanel, anything with an API. Channels keep your data fresh.
What it is
A data source in osFoundry is a channel that pulls records from an external system and keeps them fresh. You connect something that speaks an API — Stripe, Postgres, Mixpanel, or any REST endpoint — and osFoundry syncs it into a workspace channel your chat, agents, apps, and knowledge base can all read. Because the connection is a channel rather than a one-off export, you set it up once and reuse it everywhere, and the data updates on its own instead of going stale the moment you download it.\n\nSetup is concrete. For an API source you give the URL and HTTP method (GET, POST, PUT), choose an auth style — none, bearer token, API key header, or basic auth — and add any custom headers the endpoint needs. Then you pick how often it refreshes: monthly, weekly, daily, every 6 hours, hourly, or as fast as every 15 or 5 minutes, with the tighter intervals gated behind higher sync tiers. If the source pushes to you instead, create a webhook endpoint with a signing secret for HMAC verification, an optional IP allowlist, and a maximum payload size. You can also skip APIs entirely: enter rows manually through the UI or upload CSV files for batch import, and those manual and CSV sources stay local on your device. osFoundry can also ingest live video feeds over RTSP, WebRTC, or HLS as a stream source.\n\nThis matters because osFoundry is bring-your-own-key and local-first. You connect sources with your own credentials, there is no reseller sitting between you and Stripe or your Postgres box, and manual and CSV data never has to leave your machine. The result is one place where the numbers agents reason over are the same live numbers your dashboards show, kept current by a schedule you control rather than by remembering to re-export.
Key capabilities
- Connect any REST API as a data source: set the URL and method, add bearer token, API key header, or basic auth, and pass custom headers
- Sync on a schedule you pick — from monthly down to every 5 minutes — so agents and chat always read current data instead of a stale export
- Receive pushed data with signed webhook endpoints, IP allowlists, HMAC signature verification, and a payload size cap
- Import without an API too: type rows in manually or upload CSV files, which stay local on your device
- Each source is a channel you can reference from chat, agents, knowledge, and apps — one connection, reused everywhere in the workspace
Use cases
- Founder: connect Stripe and Mixpanel as data sources so an agent can answer "what changed in revenue and activation this week" against live figures, not last month's CSV
- Data engineer: point a data source at an internal Postgres-backed API with bearer auth and a 15-minute sync, then query it from chat without building a separate BI pipeline
- Ops lead: expose a signed webhook endpoint so an upstream system pushes order events into a channel that agents and apps watch in near real time
Frequently asked questions
Which data sources can I connect?
Anything with a REST API — Stripe, Mixpanel, a Postgres-backed API, or your own internal service — plus non-API options: manual entry, CSV upload, and live video streams over RTSP, WebRTC, or HLS. For API sources you configure the URL, method, and auth (bearer, API key header, or basic), so any endpoint you can call, you can sync.
How often does the data refresh?
You choose the sync interval per source, from monthly up to every 5 minutes. Lower-frequency schedules (monthly, weekly, daily) are available on lighter tiers; sub-hourly refresh such as every 15 or 5 minutes requires a real-time sync tier. Webhook sources update whenever the upstream system pushes an event.
Does my data stay private, and do I need osFoundry's keys?
osFoundry is bring-your-own-key: you connect each source with your own API credentials, so there's no reseller markup and no third party between you and the source. Manual and CSV sources stay local on your device, and webhook endpoints support HMAC signing and IP allowlists so only trusted callers can post data.