# Create an authenticated tool run stub

> Create an authenticated tool run stub.

Source: https://docs.vigilbase.com/one/api/reference/tools/post-tools-tool-name-runs

`POST https://one.vigilbase.com/api/tools/{toolName}/runs`

Create an authenticated tool run stub. Gated by requireToolRunAccessContext (read:services), matching execute.

## Authorizations

Send one of these:

- `Authorization` (string, header, required): Bearer access token from Vigilbase Identity (`auth.vigilbase.com`), sent as `Authorization: Bearer <token>`. The CLI gets one with `vigilbase login`.
- `Authorization` (string, header, required): Organisation API key (`vb_one_…`) from **Settings → API keys** in Vigilbase One, sent as `Authorization: Bearer vb_one_…`. Needs a key with write access: read-only keys get `403` with the code `read_only_key`. See [organisation API keys](https://docs.vigilbase.com/one/api#organisation-api-keys).

## Path parameters

- `toolName` (string, required)

## Body (application/json)

Validation schema (Zod source):

```ts
CreateRunSchema = z.object({
  target: z.string().min(1),
  targetType: ToolRunTargetTypeSchema.optional(),
  metadata: z.record(z.string(), z.unknown()).optional(),
})
```

## Responses

### 200

Success

### 401

Authentication required

### 403

Not permitted

## Example request

```bash
# Token from `vigilbase login`, or a write API key (vb_one_…)
curl --request POST \
  --url 'https://one.vigilbase.com/api/tools/{toolName}/runs' \
  --header "Authorization: Bearer $VIGILBASE_TOKEN" \
  --header 'Content-Type: application/json' \
  --data '{}'
```