Build with a coding agent

A coding agent can write the sender in your app’s own language and framework. The running integration is ordinary server code; it does not call an AI model to deliver each record.

Start in your app’s repository

1. In Ediphai Console, add your app under Settings → Integrations → Custom apps. Save the test key in your server’s secret store as EDIPHAI_API_KEY.
2. In Console, expand Using a coding agent like Claude Code, Codex, or similar? after adding the app or from its Keys tab. Click Copy prompt and paste it into a coding agent session in your app’s repository. The prompt includes your app’s slug and the links to the current contract, but not the key.
3. Tell the agent where your app completes records and where its server jobs run, if you know. The agent should inspect the code and report its field mapping and test results before you use a live key.

The copied prompt directs the agent to read the agent skill, supported record types and OpenAPI contract; implement a server-side sender with durable retries; and run the sender self-test with the test key. Use it with Claude Code, Codex, Cursor or another coding agent that can read these links and your app’s repository.

If the agent cannot open a URL, provide the linked agent skill, OpenAPI file and relevant guide pages directly. Fern also serves each guide as Markdown by adding .md to its URL, and llms.txt lists the entry points.

Review before going live

Check that the mapping reflects your app’s real instrument and person IDs, the outbox survives a failed send, and all sender self-test results are explained. A test receipt proves request handling only. Your church can then create a separate live key and verify the first live result in Ediphai.