Skip to main content
Cursor can write your Encrata integration once it knows the API. Point it at Encrata’s auth.md - a machine-readable contract of how to authenticate and which endpoints exist - and Cursor generates working code against it.

Prerequisites

1

Get an API key

Create one in the dashboard or read Authentication. Keys start with enc_.
2

Install Cursor

Download it from cursor.com and open your project.

Set up

1

Give Cursor the API contract

Add Encrata’s auth.md to Cursor’s context, either as an indexed doc source (Settings → add a doc → https://developer.encrata.com/auth.md) or by pasting the URL into a chat. It tells Cursor how to authenticate and lists every endpoint with its request and response shape.
2

Store your key as an environment variable

Never hard-code the key. Keep it in your environment so Cursor’s generated code reads it from there.
3

Ask Cursor to build against the API

Describe the integration you want. Cursor uses auth.md to get the endpoint, request body, and auth header right.

Generate an Encrata email validator

The generated request should hit https://developer.encrata.com/api/lookup/email/validity with an Authorization: Bearer enc_... header. If Cursor invents a different path, re-share auth.md so it works from the contract, not memory.

Next steps

auth.md for developers

The full pattern for pointing an agent at Encrata.

Examples

Copy-paste recipes for every lookup.

Authentication

Create and manage your API keys.

API reference

Every endpoint’s request and response schema.