> For the complete documentation index, see [llms.txt](https://docs.sectoral.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sectoral.xyz/using-sectoral/developer-settings.md).

# Developer Settings

From the API Keys screen you can create credentials and register webhook endpoints without writing a single request by hand. It is the in-app counterpart to the [API Reference](/developer-api/auth-and-keys.md).

***

## Creating a key

Click **+ New key**, give it a name (for example `Production`), and choose an environment:

| Environment | Prefix     | Scope                                                |
| ----------- | ---------- | ---------------------------------------------------- |
| Live        | `hc_live_` | Actual USDG and actual transfers                     |
| Test        | `hc_test_` | Robinhood Chain testnet, with no real funds involved |

You will see the full key only once, immediately after it is created, so copy it before closing the panel. We store just a hash, which means nobody can recover the key afterward, ourselves included. If you lose it, revoke it and create a new one. That is not a flaw; it is exactly how secure key handling should work.

***

## Revoking a key

Clicking **Revoke** next to an active key disables it immediately and permanently, and any request that uses it afterward will fail. Revoked keys stay in the list with a **Revoked** label so your audit history remains complete.

***

## Adding a webhook

Under Webhooks, **+ Add endpoint** prompts you for:

* An HTTPS URL that will receive deliveries
* Which events to subscribe to: `transfer.settled`, `transfer.failed`, `payment.received`, `policy.limit_reached`

Each endpoint receives only the event types you select. You can add as many endpoints as your consumers require (one forwarding to Slack, another feeding a billing system, and so on), each subscribed to its own set.

***

## Managing endpoints

You can switch any endpoint between **Active** and **Inactive**, or delete it. Setting it to inactive pauses deliveries but keeps its configuration, which is handy while you fix the receiving side. Deleting it removes it permanently.

***

## Event and payload reference

This screen handles keys and endpoints and nothing more. For the list of events, payload formats, and signature verification, see [Real-Time Event Stream](/ai-agents/event-stream.md) and the [Webhooks API](/developer-api/webhooks.md).

***

## Read on

* [Authentication and API Keys](/developer-api/auth-and-keys.md)
* [Real-Time Event Stream](/ai-agents/event-stream.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sectoral.xyz/using-sectoral/developer-settings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.