Connections
Your app. Your tools.
Your agent.
Bring events home and work with them locally. Here’s what works today, and where we could take it next.
Start with your app and your agent.
Capture with the SDK or HTTP API. New events are sealed into archives about every 10 minutes; sync them with the CLI, then let your agent query the local data. Agent entries describe CLI workflows.
Browser and Node event capture. Install the private SDK from source.
Setup guide ↗Send canonical events as NDJSON to your configured backend.
Setup guide ↗
%20--%3e%3cdefs%3e%3cstyle%3e%20.st0%20{%20fill:%20%2326251e;%20}%20%3c/style%3e%3c/defs%3e%3cpath%20class='st0'%20d='M457.43,125.94L244.42,2.96c-6.84-3.95-15.28-3.95-22.12,0L9.3,125.94c-5.75,3.32-9.3,9.46-9.3,16.11v247.99c0,6.65,3.55,12.79,9.3,16.11l213.01,122.98c6.84,3.95,15.28,3.95,22.12,0l213.01-122.98c5.75-3.32,9.3-9.46,9.3-16.11v-247.99c0-6.65-3.55-12.79-9.3-16.11h-.01ZM444.05,151.99l-205.63,356.16c-1.39,2.4-5.06,1.42-5.06-1.36v-233.21c0-4.66-2.49-8.97-6.53-11.31L24.87,145.67c-2.4-1.39-1.42-5.06,1.36-5.06h411.26c5.84,0,9.49,6.33,6.57,11.39h-.01Z'/%3e%3c/svg%3e){kind=small}
More of your stack, together.
These connections are ideas being explored. They are not available to connect, and have no announced release dates.
More ways to capture
A dedicated capture SDK.
Capture from Python applications.
Bring CSV, Parquet, JSONL, and logs.
Product analytics inputs
Bring existing product events into Slurp.
Bring existing product events into Slurp.
Bring existing product events into Slurp.
Bring existing product events into Slurp.
Errors and support inputs
Errors and releases.
Errors and stability.
Support conversations and transcripts.
Feedback directly from users.
Business and code inputs
Payments and subscriptions.
Pushes, pull requests, and releases.
Issues and cycles.
Pipeline inputs
Translate incoming tool payloads into events.
Receive events from your pipelines.
Outputs and agent destinations
Deliver events to your own endpoint.
Alerts in a channel.
Create an issue from a finding.
Open an issue or pull request.
Route relevant events to an agent.
Route relevant events to an agent.
Route relevant events to an agent.
Route relevant events to an agent.
Route relevant events to an agent.
Something that notices.
Jev is an idea for classifying incoming events and routing useful signals to an agent. This workflow is illustrative; processing and alert delivery are not available.
Events arrive
From your app and future connections.
Jev classifies
Identify a possible signal and its confidence.
Alerts go out
Hand the evidence to an agent or endpoint.
Illustrative signals: a spike in export failures, a new error pattern, stalled onboarding, or possible churn.
Get started with what works today ↗