Deploy and Host Record Key Dedup on Railway

Keep the first record for each supplied key.

About Hosting Record Key Dedup

This is a stateless JSON tool. Deploy it, copy TOOL_TOKEN from service variables and send it as an Authorization: Bearer header on POST /run. The /health endpoint is public and returns readiness only. Inputs are limited to 64 KiB. The application does not store requests or call a model.

Why Deploy Record Key Dedup

Call a deterministic operation from an agent, workflow or application without an LLM API key.

Common Use Cases

Keep the first record for each supplied key.
Insert a deterministic check or transformation in a workflow.
Repeat the documented example in a regression check.

Dependencies for Record Key Dedup

Python 3.13 container and a Railway project.
An HTTP client with your generated bearer token.

Example input for POST /run

{"rows": [{"id": 1}, {"id": 1}], "key": "id"}

Expected response

{"result": [{"id": 1}]}

The single process is intended for small internal workloads. Set concurrency and load limits upstream before serving high volume traffic.