feat: add apify api subcommand for direct API access (#1076)

## Summary

Adds `apify api` — a general-purpose authenticated HTTP client for the
Apify API, inspired by `gh api`.

- `apify api v2/users/me` — make authenticated GET requests
- `apify api v2/acts --method POST --body '{...}'` — create resources
- `apify api --list-endpoints` — browse all 129 API endpoints (from
bundled OpenAPI spec)

### Features
- HTTP methods via `--method` / `-X` (GET, POST, PUT, PATCH, DELETE)
- Request body via `--body` / `-d` (JSON string or stdin with `-`)
- Custom headers via `--header` / `-H`
- `--list-endpoints` / `-l` — lists all available endpoints with
color-coded methods and descriptions, powered by the Apify OpenAPI spec
fetched at build time

Closes #1075

Author: patrikbraborec

docs/reference.md

@@ -44,6 +44,52 @@ FLAGS
                          not provided, the latest version will be used.
 ```
 
+##### `apify api`
+
+```sh
+DESCRIPTION
+  Makes an authenticated HTTP request to the Apify API and prints the response.
+  The endpoint can be a relative path (e.g. "acts", "v2/acts", or "/v2/acts").
+  The "v2/" prefix is added automatically if omitted.
+
+  You can also pass the HTTP method before the endpoint:
+    apify api GET /v2/actor-runs
+    apify api POST /v2/acts -d '{"name": "my-actor"}'
+
+  Use --params/-p to pass query parameters as JSON:
+    apify api actor-runs -p '{"limit": 1, "desc": true}'
+
+  Use --list-endpoints to see all available API endpoints.
+  For full documentation, see https://docs.apify.com/api/v2
+
+USAGE
+  $ apify api [methodOrEndpoint] [endpoint] [-d <value>] [-H <value>]
+              [-l] [-X GET|POST|PUT|PATCH|DELETE] [-p <value>]
+
+ARGUMENTS
+  methodOrEndpoint  The API endpoint path (e.g. "acts",
+                    "v2/acts", "/v2/users/me"), or an HTTP method followed by the
+                    endpoint (e.g. "GET /v2/users/me").
+  endpoint          The API endpoint path when the first
+                    argument is an HTTP method.
+
+FLAGS
+  -d, --body=<value>     The request body (JSON string). Use
+                         "-" to read from stdin.
+      -H, --header=<value>   Additional HTTP header(s). Pass a
+                         single "key:value" string, or a JSON object like '{"X-Foo":
+                         "bar", "X-Baz": "qux"}' to send multiple headers. The flag
+                         can only be used once; use the JSON form for multiple
+                         headers.
+  -l, --list-endpoints   List all available Apify API
+                         endpoints.
+      -X, --method=<option>  The HTTP method to use. Defaults to
+                         GET.
+                         <options: GET|POST|PUT|PATCH|DELETE>
+  -p, --params=<value>   Query parameters as a JSON object,
+                         e.g. '{"limit": 1, "desc": true}'.
+```
+
 ##### `apify telemetry`
 
 ```sh

scripts/generate-cli-docs.ts

@@ -75,6 +75,7 @@ const categories: Record<string, CommandsInCategory[]> = {
 		//
 		{ command: Commands.help },
 		{ command: Commands.upgrade },
+		{ command: Commands.api },
 		{ command: Commands.telemetry },
 		{ command: Commands.telemetryEnable },
 		{ command: Commands.telemetryDisable },

src/commands/_register.ts

@@ -9,6 +9,7 @@ import { ActorGetValueCommand } from './actor/get-value.js';
 import { ActorPushDataCommand } from './actor/push-data.js';
 import { ActorSetValueCommand } from './actor/set-value.js';
 import { ActorsIndexCommand } from './actors/_index.js';
+import { ApiCommand } from './api.js';
 import { AuthIndexCommand } from './auth/_index.js';
 import { BuildsIndexCommand } from './builds/_index.js';
 import { TopLevelCallCommand } from './call.js';
@@ -49,6 +50,7 @@ export const apifyCommands = [
 	TelemetryIndexCommand,
 
 	// top-level
+	ApiCommand,
 	TopLevelCallCommand,
 	UpgradeCommand,
 	InstallCommand,