Connect a custom tool

Use the API if you want your own tool to read Nightcrew data. For most people, chat or an MCP connection is the easier starting point.

Create a token under account. Send it in the Authorization header. A token can access only the issuing account's records.

Base URL: https://nightcrew.news/api/v1

Request	What it gives you
`GET /me`	The connected account and token permissions
`GET /signals?q=identity&limit=10`	Matching stories and source links
`GET /insights?limit=10`	Insights and their supporting evidence
`GET /people?q=cloud&limit=10`	Matching people in your directory
`GET /sources`	Your sources and their status
`GET /status`	Your account's collection status

curl 'https://nightcrew.news/api/v1/insights?limit=5' \
  -H "Authorization: Bearer $NIGHTCREW_API_TOKEN"

Set NIGHTCREW_API_TOKEN in your tool's private environment. Keep credentials out of shared code and messages.

Ask a question

Enable allow AI queries when creating a token if your tool needs to ask Nightcrew's AI questions.

curl 'https://nightcrew.news/api/v1/query' \
  -H "Authorization: Bearer $NIGHTCREW_API_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"question":"Which recent security stories could help with a CISO newsletter?"}'

Review generated answers against their source links. AI questions are subject to account usage limits.

If a request fails

401: check whether the token is missing, expired, or revoked.
403: check that the token has permission for the request.
404: the item isn't available in your account.
422: check the request fields.
429: wait before trying again.
503: the service couldn't complete the request; try again later.

Revoke a token in account when your tool no longer needs it. The API doesn't send emails or publish posts.