electric.ax valid

Electric

Electric provides the data primitives and infra to build collaborative, multi-agent systems. Including Postgres Sync, Durable Streams, TanStack DB and PGlite.

For agents: Electric, data primitives and sync infrastructure for multi-agent systems: Postgres Sync, Durable Streams, TanStack DB, PGlite, with HTTP API and TypeScript cli

postgres syncreal-time streamsmulti-agent systemstypescript clienthttp api

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T00:52:50.155Z. Cached copy · Source on electric.ax

# Electric

> Electric provides the data primitives and infra to build collaborative, multi-agent systems. Including Postgres Sync, Durable Streams, TanStack DB and PGlite.

> [!IMPORTANT] Instructions for coding agents
> Coding agents should read [AGENTS.md](/AGENTS.md) for instructions and guidance.

## Table of Contents

### Hosted products

- [Electric Streams](/streams.md): The data primitive for the agent loop. Persistent, addressable, real-time streams over plain HTTP.
- [Electric Sync](/sync.md): Composable sync primitives for multi-agent systems — Postgres Sync, TanStack DB and PGlite.

### Sync primitives

- [Postgres Sync](/sync/postgres-sync.md): Read-path sync engine for Postgres that handles partial replication, data delivery and fan-out.
- [TanStack DB](/sync/tanstack-db.md): Reactive client store for building super-fast apps. With sub-millisecond reactivity and instant local writes.
- [PGlite](/sync/pglite.md): Embeddable Postgres with reactivity and sync. For a full database inside your client or runtime.

### Guides

- [Auth - Guide](/docs/sync/guides/auth.md): How to do authentication and authorization with Electric.
- [Shapes - Guide](/docs/sync/guides/shapes.md): Shapes are the core primitive for controlling sync in the ElectricSQL system.
- [Writes - Guide](/docs/sync/guides/writes.md): How to do local writes and write-path sync with Electric.
- [Installation - Guide](/docs/sync/guides/installation.md): How to install and run Electric.
- [PostgreSQL Permissions - Guide](/docs/sync/guides/postgres-permissions.md): How to create and configure PostgreSQL users with the necessary permissions for Electric.
- [Deployment - Guide](/docs/sync/guides/deployment.md): How to deploy the Electric sync engine.
- [Upgrading - Guide](/docs/sync/guides/upgrading.md): How to upgrade the Electric sync service with minimal disruption.
- [Sharding - Guide](/docs/sync/guides/sharding.md): How to use Electric with sharded PostgreSQL databases.
- [Security - Guide](/docs/sync/guides/security.md): How to secure data access and encrypt data with Electric.
- [Troubleshooting - Guide](/docs/sync/guides/troubleshooting.md): Tips and FAQs on how to run Electric successfully.
- [Client development - Guide](/docs/sync/guides/client-development.md): How to write an Electric client for any language that speaks HTTP and JSON.

### API

- [HTTP API](/docs/sync/api/http.md): The HTTP API is the primary, low level API for syncing data with Electric.
- [Sync service](/docs/sync/api/config.md): Configuration options for the Electric sync engine.

#### Clients

- [Typescript Client](/docs/sync/api/clients/typescript.md): Electric provides an Typescript client for streaming Shapes from Postgres into the web browser and other Javascript environments.
- [Elixir Client](/docs/sync/api/clients/elixir.md): Electric provides an Elixir client and a Phoenix integration.

### Integrations

#### Frameworks

- [LiveStore - Integrations](/docs/sync/integrations/livestore.md): H
…

Related sites

Other listed sites in AI agents and MCP. See the whole category →

Machine-readable: GET /v1/resolve?q=electric.ax · GET /v1/domain/electric.ax · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for electric.ax:
1. POST https://agentwebmap.com/v1/sites/electric.ax/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://electric.ax/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/electric.ax/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/electric.ax).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.