> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.nativeport.ai/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.nativeport.ai/_mcp/server.

# Linkup

Fronts the Search API of [Linkup](https://linkup.so); the gateway supplies Linkup's `/v1` base itself:

```
POST /linkup/search   → https://api.linkup.so/v1/search
```

Only `POST` is mounted. Controls such as `q`, `depth`, and `outputType` live in the JSON body, which is relayed without modification.

## Credential handling

Linkup reads its key from `Authorization: Bearer` — the very header carrying your gateway token — so the gateway **replaces** that header with the Linkup key:

* **`Authorization` is overwritten with Linkup's secret key.** Your gateway token stops at the gateway and never travels upstream.
* No query-param form of the key exists on Linkup's side, so nothing gets removed from the query string.

## Example

```bash
curl -X POST "$GATEWAY/linkup/search" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"q": "latest cloudflare workers features", "depth": "standard", "outputType": "searchResults"}'
```

Responses arrive as Linkup's JSON, untouched. Field-level request and response detail lives in [Linkup's documentation](https://docs.linkup.so); the gateway modifies neither.