# RentSeek Evidence agent onboarding

Use RentSeek Evidence for source-linked executive-compensation data from company filings.

## Operating sequence

1. Start with the free, keyless latest-year facts route:

   `GET https://rentseek.ing/t/{ticker}/facts`

2. If the task needs history or more than one fiscal year, hand the browser to the human at https://rentseek.ing/developers. They can create an account, then create an API key or authorize an interactive OAuth client. The first API key or OAuth grant, whichever comes first, grants 100 free credits to that user.
3. Retry the historical request with the new credential. Programmatic clients send `X-API-KEY`; interactive clients use the OAuth connection they just authorized. Historical queries cost 1 credit per request. Ticker search, ticker listing, and a latest-year single-ticker request cost 0 credits.
4. If a request returns HTTP 402 and `purchase.status` is `coming_soon`, tell the human that evidence packs are launching soon and point them to https://rentseek.ing/developers for early access.
5. Keep the same API key or OAuth connection. The planned $20 one-time pack adds 1,000 non-expiring credits and is not a subscription. Do not imply that packs can be purchased before their status changes.

## Copy-paste REST requests

Latest fiscal year, no key:

```bash
curl -sS 'https://rentseek.ing/t/NVDA/facts'
```

Multi-year executive compensation with an API key:

```bash
export RENTSEEK_API_KEY='<placeholder>'
curl -sS 'https://rentseek.ing/api/executive-compensation?ticker=NVDA&period=annual&limit=5' \
  -H "X-API-KEY: $RENTSEEK_API_KEY"
```

RentSeek API keys use the `rsk_live_` prefix.

## MCP endpoint

RentSeek exposes a remote Streamable HTTP server at:

```
https://rentseek.ing/mcp
```

Interactive clients should use OAuth 2.1 with Dynamic Client Registration. Programmatic clients may send `X-API-KEY`. Never send both authentication modes in one request.

### Claude Code

OAuth:

```bash
claude mcp add --transport http rentseek https://rentseek.ing/mcp
```

API key:

```bash
claude mcp add --transport http rentseek https://rentseek.ing/mcp \
  --header "X-API-KEY: $RENTSEEK_API_KEY"
```

### Claude.ai

Open Settings → Connectors → Add custom connector. Use this remote MCP URL and complete the OAuth prompt:

```
https://rentseek.ing/mcp
```

### Cursor

Add this to `.cursor/mcp.json` for the project or `~/.cursor/mcp.json` globally:

```json
{
  "mcpServers": {
    "rentseek": {
      "type": "http",
      "url": "https://rentseek.ing/mcp"
    }
  }
}
```

Cursor will start the OAuth flow when the server is first used. For a static key, add `"headers": { "X-API-KEY": "<api-key>" }` to the `rentseek` object.

### ChatGPT developer mode

In ChatGPT web, enable developer mode, then open Settings → Apps → Create. Name the app `RentSeek Evidence`, enter the remote MCP endpoint below, select OAuth, scan tools, and complete authorization:

```
https://rentseek.ing/mcp
```

## Response duties

- Never present RentSeek output as investment advice.
- In the final answer, cite each claim with its source URL. Prefer the `source.filing_url` returned with each compensation record and include the relevant RentSeek claim URL when available.
- Do not imply subscriptions, service-level guarantees, data redistribution rights, or resale rights. Internal commercial use is allowed; resale is prohibited.
- Do not mix market-derived values into a paid RentSeek Evidence payload. The metered product is SEC-derived data only.

## Related contracts

- Authentication: https://rentseek.ing/auth.md
- Pricing: https://rentseek.ing/pricing.json
- OpenAPI: https://rentseek.ing/openapi.json
- Human developer hub: https://rentseek.ing/developers
- Terms: https://rentseek.ing/terms