Slicegraph for Clay

Clay is where most teams assemble a prospect list; the part it cannot supply is why now. Slicegraph adds the timing layer: dated events from official Dutch and Belgian registers, resolved to a company registration number so they join cleanly onto what you already have.

Pull: an HTTP API enrichment column

Start from a table that already has a KvK or KBO number. Add an HTTP API column pointing at the signals endpoint, map the newest event into its own column, and trigger sequences on freshness rather than on the whole table.

GET https://slicegraph.com/api/v1/signals?kvk={{KvK column}}
Authorization: Bearer sg_live_...

Push: a webhook into a Clay table

For coverage beyond the accounts you already track, register a webhook subscription against a Clay table's webhook source. Every new matching signal arrives as a row, signed so you can verify it.

POST https://slicegraph.com/api/v1/subscriptions
Authorization: Bearer sg_live_...

{ "url": "https://api.clay.com/...", "filter": { "family": "einvoicing" } }

How this differs from the providers already in Clay

Clay's built-in enrichment answers who a company is. This answers what just happened to it, which is a different question and a different data shape.

Slicegraph compared with the firmographic and contact providers already available inside Clay, on what each one answers, how fresh it is, and how records are matched.
Aspect	Slicegraph	Typical Clay provider
Question answered	What happened to this company, and when	Who this company is, and who works there
Freshness	Daily, dated to the official publication	Periodic refresh, rarely dated
Matching	Exact on KvK or KBO registration number	Usually domain or company name
Coverage	Netherlands and Belgium, official registers only	Global, mixed sourcing
Personal data	None: company level only	Contact records are the product

Every plan includes an API key that works in Clay from the first request. See pricing.