@ivannxbt/ai-config 0.1.0

package/.agents/skills/use-railway/references/operate.md

@@ -0,0 +1,159 @@
+# Operate
+
+Check health, read logs, query metrics, and troubleshoot failures.
+
+## Health snapshot
+
+Start broad, then narrow:
+
+```bash
+railway status --json                                    # linked context
+railway service status --all --json                      # all services, deployment states
+railway deployment list --limit 10 --json                # recent deployments
+```
+
+Deployment statuses: `SUCCESS`, `BUILDING`, `DEPLOYING`, `FAILED`, `CRASHED`, `REMOVED`.
+
+If everything looks healthy, return a summary and stop. If something is degraded or failing, continue to log inspection.
+
+## Logs
+
+### Recent logs
+
+```bash
+railway logs --service <service> --lines 200 --json              # runtime logs
+railway logs --service <service> --build --lines 200 --json      # build logs
+railway logs --latest --lines 200 --json                         # latest deployment
+```
+
+`railway logs` streams indefinitely when no bounding flags are given. Always use `--lines`, `--since`, or `--until` to get a bounded fetch. Open streams block execution.
+
+### Time-bounded queries
+
+```bash
+railway logs --service <service> --since 1h --lines 400 --json
+railway logs --service <service> --since 30m --until 10m --lines 400 --json
+```
+
+### Filtered queries
+
+Use `--filter` to narrow logs without scanning everything manually:
+
+```bash
+railway logs --service <service> --lines 200 --filter "@level:error" --json
+railway logs --service <service> --lines 200 --filter "@level:warn AND timeout" --json
+railway logs --service <service> --lines 200 --filter "connection refused" --json
+```
+
+Filter syntax supports text search (`"error message"`), attribute filters (`@level:error`, `@level:warn`), and boolean operators (`AND`, `OR`, `-` for negation). Full syntax: https://docs.railway.com/guides/logs
+
+### Scoped by environment
+
+```bash
+railway logs --service <service> --environment <env> --lines 200 --json
+```
+
+## Metrics
+
+Resource usage metrics (CPU, memory, network, disk) are only available through the GraphQL API:
+
+```bash
+scripts/railway-api.sh \
+  'query metrics($environmentId: String!, $serviceId: String, $startDate: DateTime!, $groupBy: [MetricTag!], $measurements: [MetricMeasurement!]!) {
+    metrics(environmentId: $environmentId, serviceId: $serviceId, startDate: $startDate, groupBy: $groupBy, measurements: $measurements) {
+      measurement tags { serviceId deploymentId region } values { ts value }
+    }
+  }' \
+  '{"environmentId":"<env-id>","serviceId":"<service-id>","startDate":"2026-02-19T00:00:00Z","measurements":["CPU_USAGE","MEMORY_USAGE_GB"]}'
+```
+
+Available measurements: `CPU_USAGE`, `CPU_LIMIT`, `MEMORY_USAGE_GB`, `MEMORY_LIMIT_GB`, `NETWORK_RX_GB`, `NETWORK_TX_GB`, `DISK_USAGE_GB`, `EPHEMERAL_DISK_USAGE_GB`, `BACKUP_USAGE_GB`.
+
+Omit `serviceId` and add `"groupBy": ["SERVICE_ID"]` to query all services in the environment at once. Get the environment and service IDs from `railway status --json`.
+
+## Failure triage
+
+When something is broken, classify the failure first. The fix depends on the class.
+
+### Build failures
+
+The service failed to build. Look at build logs:
+
+```bash
+railway logs --latest --build --lines 400 --json
+```
+
+Common causes and fixes:
+- **Missing dependencies**: check lockfiles, verify package manager detection
+- **Wrong build command**: override with `railway environment edit --service-config <service> build.buildCommand "<command>"`
+- **Builder mismatch**: switch builders with `railway environment edit --service-config <service> build.builder RAILPACK`
+- **Wrong root directory** (monorepo): set `source.rootDirectory` to the correct package path
+
+### Runtime failures
+
+The build succeeded but the service crashes or misbehaves:
+
+```bash
+railway logs --latest --lines 400 --json
+railway logs --service <service> --since 1h --lines 400 --json
+```
+
+Common causes and fixes:
+- **Bad start command**: override with `railway environment edit --service-config <service> deploy.startCommand "<command>"`
+- **Missing runtime variable**: check `railway variable list --service <service> --json` and set missing values
+- **Port mismatch**: the service must listen on `$PORT` (Railway injects this). Verify with logs.
+- **Upstream dependency down**: check other services' status and logs
+
+### Config-driven failures
+
+Something worked before and broke after a config change:
+
+```bash
+railway environment config --json
+railway variable list --service <service> --json
+```
+
+Compare the config against expected values. Look for changes that may have introduced the regression.
+
+### Networking failures
+
+Domain returns errors, or service-to-service calls fail:
+
+```bash
+railway domain --service <service> --json
+railway logs --service <service> --lines 200 --json
+```
+
+Check: target port matches what the service listens on, domain status is healthy, private domain variable references are correct.
+
+## Recovery
+
+After identifying the cause, fix and verify:
+
+```bash
+# Fix (examples)
+railway environment edit --service-config <service> deploy.startCommand "<correct-command>"
+railway variable set MISSING_VAR=value --service <service>
+
+# Redeploy
+railway redeploy --service <service> --yes
+
+# Verify
+railway service status --service <service> --json
+railway logs --service <service> --lines 200 --json
+```
+
+Always verify after fixing. Don't assume the redeploy succeeded.
+
+## Troubleshoot common blockers
+
+- **Unlinked context**: `railway link --project <id-or-name>`
+- **Missing service scope for logs**: pass `--service` and `--environment` explicitly
+- **No deployments found**: the service exists but has never deployed, create an initial deploy first
+- **Metrics query returns empty**: verify IDs from `railway status --json` and check the time window
+- **Config patch type error**: check the typed paths in [configure.md](configure.md), for example, `numReplicas` is an integer, not a string
+
+## Validated against
+
+- Docs: [status.md](https://docs.railway.com/cli/status), [logs.md](https://docs.railway.com/cli/logs), [observability.md](https://docs.railway.com/observability), [observability/logs.md](https://docs.railway.com/observability/logs), [observability/metrics.md](https://docs.railway.com/observability/metrics)
+- CLI source: [status.rs](https://github.com/railwayapp/cli/blob/a8a5afe/src/commands/status.rs), [logs.rs](https://github.com/railwayapp/cli/blob/a8a5afe/src/commands/logs.rs), [deployment.rs](https://github.com/railwayapp/cli/blob/a8a5afe/src/commands/deployment.rs), [redeploy.rs](https://github.com/railwayapp/cli/blob/a8a5afe/src/commands/redeploy.rs)

package/.agents/skills/use-railway/references/request.md

@@ -0,0 +1,238 @@
+# Request
+
+Official documentation and community endpoints. GraphQL operations for things the CLI doesn't expose.
+
+## Official documentation
+
+Primary sources for authoritative Railway information:
+
+- **Full LLM docs**: `https://docs.railway.com/api/llms-docs.md`
+- **LLM summary**: `https://railway.com/llms.txt`
+- **Templates**: `https://railway.com/llms-templates.md`
+- **Changelog**: `https://railway.com/llms-changelog.md`
+- **Blog**: `https://blog.railway.com/llms-blog.md`
+- **Direct doc pages**: `https://docs.railway.com/<path>` (for example, `cli/up`, `networking/domains`, `observability/logs`)
+
+Tip: append `.md` to any `docs.railway.com` page URL to get a markdown version suitable for LLM consumption.
+
+Common doc paths:
+
+| Topic | Path |
+|---|---|
+| Projects | `guides/projects` |
+| Deployments | `guides/deployments` |
+| Volumes | `guides/volumes` |
+| Variables | `guides/variables` |
+| CLI reference | `reference/cli-api` |
+| Pricing | `reference/pricing` |
+| Public networking | `networking/public-networking` |
+| Private networking | `networking/private-networking` |
+
+Fetch official docs first for product behavior questions. Use Central Station only when you need community evidence, prior incidents, or implementation anecdotes.
+
+
+## Central Station (community)
+
+Search and browse Railway's community platform for prior discussions, issue patterns, and field solutions.
+
+### Recent threads
+
+```bash
+curl -s 'https://station-server.railway.com/gql' \
+  -H 'content-type: application/json' \
+  -d '{"query":"{ threads(first: 10, sort: recent_activity) { edges { node { slug subject status upvoteCount createdAt topic { slug displayName } } } } }"}'
+```
+
+Filter by topic with the `topic` parameter (`"questions"`, `"feedback"`, `"community"`, `"billing"`):
+
+```bash
+curl -s 'https://station-server.railway.com/gql' \
+  -H 'content-type: application/json' \
+  -d '{"query":"{ threads(first: 10, sort: recent_activity, topic: \"questions\") { edges { node { slug subject status topic { displayName } upvoteCount } } } }"}'
+```
+
+Sort options: `recent_activity` (default), `newest`, `highest_votes`.
+
+### Search threads
+
+```bash
+curl -s 'https://station-server.railway.com/gql' \
+  -H 'content-type: application/json' \
+  -d '{"query":"{ threads(first: 10, search: \"<search-term>\") { edges { node { slug subject status } } } }"}'
+```
+
+### LLM data export
+
+Bulk search alternative — fetches all public threads with full content:
+
+```bash
+curl -s 'https://station-server.railway.com/api/llms-station'
+```
+
+### Read a full thread
+
+```bash
+curl -s 'https://station-server.railway.com/api/threads/<slug>?format=md'
+```
+
+Thread URLs follow the format: `https://station.railway.com/{topic_slug}/{thread_slug}`
+
+Community threads are anecdotal. Always pair with official docs when the answer informs an operational decision.
+
+
+## GraphQL helper
+
+All GraphQL operations use the API helper script, which handles authentication automatically:
+
+```bash
+scripts/railway-api.sh '<query>' '<variables-json>'
+```
+
+The script reads the API token from `~/.railway/config.json` and sends requests to `https://backboard.railway.com/graphql/v2`.
+
+For the full API schema, see: https://docs.railway.com/api/llms-docs.md
+
+## Project mutations
+
+The CLI doesn't expose project setting updates (rename, PR deploys, visibility). Use GraphQL:
+
+```bash
+scripts/railway-api.sh \
+  'mutation updateProject($id: String!, $input: ProjectUpdateInput!) {
+    projectUpdate(id: $id, input: $input) { id name isPublic prDeploys botPrEnvironments }
+  }' \
+  '{"id":"<project-id>","input":{"name":"new-name","prDeploys":true}}'
+```
+
+Common `ProjectUpdateInput` fields: `name`, `isPublic`, `prDeploys`, `botPrEnvironments`.
+
+
+## Service mutations
+
+The CLI can create services (`railway add`) but cannot rename them or change icons. Use GraphQL:
+
+```bash
+scripts/railway-api.sh \
+  'mutation updateService($id: String!, $input: ServiceUpdateInput!) {
+    serviceUpdate(id: $id, input: $input) { id name icon }
+  }' \
+  '{"id":"<service-id>","input":{"name":"new-name"}}'
+```
+
+`ServiceUpdateInput` fields: `name`, `icon` (image URL, animated GIF, or devicons URL like `https://devicons.railway.app/postgres`).
+
+Get the service ID from `railway status --json`.
+
+
+## Service creation via GraphQL
+
+Prefer `railway add` for most cases. Use GraphQL for programmatic or advanced use:
+
+```bash
+scripts/railway-api.sh \
+  'mutation createService($input: ServiceCreateInput!) {
+    serviceCreate(input: $input) { id name }
+  }' \
+  '{"input":{"projectId":"<project-id>","name":"my-service","source":{"image":"nginx:latest"}}}'
+```
+
+`ServiceCreateInput` fields:
+
+| Field | Type | Description |
+|---|---|---|
+| `projectId` | String! | Target project (required) |
+| `name` | String | Service name (auto-generated if omitted) |
+| `source.image` | String | Docker image (for example, `nginx:latest`) |
+| `source.repo` | String | GitHub repo (for example, `user/repo`) |
+| `branch` | String | Git branch for repo source |
+| `environmentId` | String | Create only in a specific environment |
+
+After creating a service via GraphQL, configure it with a JSON config patch including `isCreated: true` (see [configure.md](configure.md)).
+
+
+## Metrics queries
+
+Resource usage metrics are only available via GraphQL:
+
+```bash
+scripts/railway-api.sh \
+  'query metrics($environmentId: String!, $serviceId: String, $startDate: DateTime!, $endDate: DateTime, $sampleRateSeconds: Int, $averagingWindowSeconds: Int, $groupBy: [MetricTag!], $measurements: [MetricMeasurement!]!) {
+    metrics(environmentId: $environmentId, serviceId: $serviceId, startDate: $startDate, endDate: $endDate, sampleRateSeconds: $sampleRateSeconds, averagingWindowSeconds: $averagingWindowSeconds, groupBy: $groupBy, measurements: $measurements) {
+      measurement tags { serviceId deploymentId region } values { ts value }
+    }
+  }' \
+  '{"environmentId":"<env-id>","serviceId":"<service-id>","startDate":"2026-02-19T00:00:00Z","measurements":["CPU_USAGE","MEMORY_USAGE_GB"]}'
+```
+
+Available `MetricMeasurement` values: `CPU_USAGE`, `CPU_LIMIT`, `MEMORY_USAGE_GB`, `MEMORY_LIMIT_GB`, `NETWORK_RX_GB`, `NETWORK_TX_GB`, `DISK_USAGE_GB`, `EPHEMERAL_DISK_USAGE_GB`, `BACKUP_USAGE_GB`.
+
+Optional parameters: `endDate` (defaults to now), `sampleRateSeconds`, `averagingWindowSeconds`. Use `groupBy: ["SERVICE_ID"]` without `serviceId` to query all services in an environment at once. Valid `MetricTag` values for `groupBy`: `SERVICE_ID`, `DEPLOYMENT_ID`, `DEPLOYMENT_INSTANCE_ID`, `REGION`.
+
+Get environment and service IDs from `railway status --json`.
+
+## Template search
+
+Search Railway's template marketplace:
+
+```bash
+scripts/railway-api.sh \
+  'query templates($query: String!, $verified: Boolean, $recommended: Boolean) {
+    templates(query: $query, verified: $verified, recommended: $recommended) {
+      edges { node { code name description category } }
+    }
+  }' \
+  '{"query":"redis","verified":true}'
+```
+
+| Parameter | Type | Description |
+|---|---|---|
+| `query` | String | Search term |
+| `verified` | Boolean | Only verified templates |
+| `recommended` | Boolean | Only recommended templates |
+| `first` | Int | Number of results (max ~100) |
+
+Common template codes: `ghost`, `strapi`, `minio`, `n8n`, `uptime-kuma`, `umami`, `postgres`, `redis`, `mysql`, `mongodb`.
+
+Deploy a found template via CLI:
+
+```bash
+railway deploy --template <template-code>
+```
+
+### GraphQL template deployment
+
+For deploying into a specific environment or tracking the workflow, use the two-step GraphQL flow:
+
+**Step 1** — Fetch the template config:
+
+```bash
+scripts/railway-api.sh \
+  'query template($code: String!) {
+    template(code: $code) { id serializedConfig }
+  }' \
+  '{"code":"postgres"}'
+```
+
+**Step 2** — Deploy with `templateDeployV2`:
+
+```bash
+scripts/railway-api.sh \
+  'mutation deploy($input: TemplateDeployV2Input!) {
+    templateDeployV2(input: $input) { projectId workflowId }
+  }' \
+  '{"input":{
+    "templateId":"<id-from-step-1>",
+    "serializedConfig":<config-object-from-step-1>,
+    "projectId":"<project-id>",
+    "environmentId":"<env-id>",
+    "workspaceId":"<workspace-id>"
+  }}'
+```
+
+`serializedConfig` is the raw JSON object from the template query, not a string. Get `workspaceId` via `scripts/railway-api.sh 'query { project(id: "<project-id>") { workspaceId } }' '{}'`.
+
+
+## Validated against
+
+- Docs: [api docs](https://docs.railway.com/api/llms-docs.md), [community.md](https://docs.railway.com/community), [cli/docs.md](https://docs.railway.com/cli/docs)
+- CLI source: [docs.rs](https://github.com/railwayapp/cli/blob/a8a5afe/src/commands/docs.rs)

package/.agents/skills/use-railway/references/setup.md

@@ -0,0 +1,195 @@
+# Setup
+
+Create, link, and organize Railway projects, services, databases, and workspaces.
+
+## Projects
+
+### List and discover
+
+```bash
+railway project list --json        # projects in current workspace
+railway list --json                # all projects across workspaces with service metadata
+railway whoami --json              # current user, workspace memberships
+```
+
+### Link to an existing project
+
+Linking sets the working context for all subsequent CLI commands in this directory.
+
+```bash
+railway link --project <project-id-or-name>
+railway status --json              # confirm linked context
+```
+
+Without `--project`, `railway link` runs interactively. For scripted or CI use, always pass explicit flags.
+
+### Link to a specific service
+
+Switch the linked service within an already-linked project:
+
+```bash
+railway service link              # interactive service picker
+railway service link <name>       # link directly by name
+```
+
+### Create a new project
+
+```bash
+railway init --name <project-name>
+railway init --name <project-name> --workspace <workspace-id-or-name>
+```
+
+`railway init` both creates and links in one step. In CI or multi-workspace setups, pass `--workspace` explicitly to avoid ambiguity.
+
+### Update project settings
+
+Settings like project name, PR deploys, and visibility aren't exposed through the CLI. Use the GraphQL API helper (see [request.md](request.md)):
+
+```bash
+scripts/railway-api.sh \
+  'mutation updateProject($id: String!, $input: ProjectUpdateInput!) {
+    projectUpdate(id: $id, input: $input) { id name isPublic prDeploys }
+  }' \
+  '{"id":"<project-id>","input":{"name":"new-name","prDeploys":true}}'
+```
+
+## Services
+
+### Create a service
+
+```bash
+railway add --service <service-name>          # empty service
+railway add --database postgres               # managed database (postgres, redis, mysql, mongodb)
+railway add                                   # interactive, prompts for type
+```
+
+Before adding a database, check for existing database services to avoid duplicates. Run `railway environment config --json` and inspect `source.image` for each service:
+
+| Image pattern | Database |
+|---|---|
+| `ghcr.io/railway/postgres*` or `postgres:*` | Postgres |
+| `ghcr.io/railway/redis*` or `redis:*` | Redis |
+| `ghcr.io/railway/mysql*` or `mysql:*` | MySQL |
+| `ghcr.io/railway/mongo*` or `mongo:*` | MongoDB |
+
+If a matching database already exists, skip creation and wire the existing service's variables to the app.
+
+Empty services have no source until you configure one. This is the right pattern when you need to set source repo, branch, or build config before the first deploy.
+
+### Connect a database to a service
+
+After `railway add --database <type>`, the database creates connection variables automatically. Wire them to your app service using variable references:
+
+| Database | Connection variable |
+|---|---|
+| Postgres | `${{Postgres.DATABASE_URL}}` |
+| Redis | `${{Redis.REDIS_URL}}` |
+| MySQL | `${{MySQL.MYSQL_URL}}` |
+| MongoDB | `${{MongoDB.MONGO_URL}}` |
+
+```bash
+railway variable set DATABASE_URL='${{Postgres.DATABASE_URL}}' --service <app-service>
+```
+
+Service names in variable references are case-sensitive and must match exactly. For full wiring details including public/private networking decisions, see [configure.md](configure.md).
+
+When creating new service instances via JSON config patches, include `isCreated: true` in the service block to mark it as a new service.
+
+### Deploy from a template
+
+Templates provision pre-configured services with sensible defaults, faster than creating an empty service and configuring it manually:
+
+```bash
+railway deploy --template <template-code>
+```
+
+Common template codes: `postgres`, `redis`, `mysql`, `mongodb`, `minio`, `umami`. For the full list, search via the GraphQL API (see [request.md](request.md)).
+
+Template deployments typically create:
+
+- A service with pre-configured image or source
+- Environment variables (connection strings, secrets)
+- A volume for persistent data (databases)
+- A TCP proxy for external access (where applicable)
+
+### Bootstrap source for an empty service
+
+After creating an empty service, wire it to a repo:
+
+```bash
+railway environment edit --service-config <service> source.repo <repo-url>
+railway environment edit --service-config <service> source.branch <branch>
+```
+
+### Deploy a Docker image
+
+When you have a built image (for example, from a private registry or Docker Hub), skip source builds entirely:
+
+```bash
+railway environment edit --service-config <service> source.image <image:tag>
+```
+
+This sets the service to pull from a container registry instead of building from source.
+
+## Analyze codebase before setup
+
+When setting up a new service from source, detect the project type from marker files:
+
+| Marker file | Type |
+|---|---|
+| `package.json` | Node.js |
+| `requirements.txt` or `pyproject.toml` | Python |
+| `go.mod` | Go |
+| `Cargo.toml` | Rust |
+| `index.html` (no package.json) | Static site |
+
+### Monorepo detection
+
+| Marker | Monorepo type |
+|---|---|
+| `pnpm-workspace.yaml` | pnpm workspace (shared) |
+| `package.json` with `workspaces` field | npm/yarn workspace (shared) |
+| `turbo.json` | Turborepo (shared) |
+| Multiple subdirectories with separate `package.json`, no workspace config | Isolated monorepo |
+
+**Isolated monorepo** (apps don't share code): set `rootDirectory` to the app's subdirectory (for example, `/apps/api`).
+
+**Shared monorepo** (TypeScript workspaces, shared packages): do not set `rootDirectory`. Set custom build and start commands instead:
+
+- pnpm: `pnpm --filter <package> build`
+- npm: `npm run build --workspace=packages/<package>`
+- yarn: `yarn workspace <package> build`
+- Turborepo: `turbo run build --filter=<package>`
+
+### Scaffolding hints
+
+When no code exists, minimal starting points for common types:
+
+- **Static site**: create `index.html` in the root directory.
+- **Vite React**: `npm create vite@latest . -- --template react`
+- **Python FastAPI**: create `main.py` with a FastAPI app and `requirements.txt` with `fastapi` and `uvicorn`.
+- **Go**: create `main.go` with an HTTP server that reads `PORT` from the environment.
+
+## Workspaces
+
+Workspaces scope billing and team access. Most users have one personal workspace and possibly team workspaces.
+
+```bash
+railway whoami --json              # lists workspace memberships
+```
+
+When creating projects, Railway uses the default workspace unless `--workspace` is specified.
+
+## Troubleshoot setup issues
+
+- **CLI missing**: install via `brew install railway` or `curl -fsSL https://railway.com/install.sh | sh`
+- **Not authenticated**: `railway login`
+- **Project not found**: verify with `railway project list --json`, check workspace context
+- **Service not found**: `railway service status --all --json` to list all services in the project
+- **Wrong workspace**: inspect `railway whoami --json`, re-run with explicit `--workspace`
+- **Permission denied**: check workspace role, mutations require member or admin access
+
+## Validated against
+
+- Docs: [cli.md](https://docs.railway.com/cli), [init.md](https://docs.railway.com/cli/init), [add.md](https://docs.railway.com/cli/add), [link.md](https://docs.railway.com/cli/link), [project.md](https://docs.railway.com/cli/project), [list.md](https://docs.railway.com/cli/list), [whoami.md](https://docs.railway.com/cli/whoami)
+- CLI source: [init.rs](https://github.com/railwayapp/cli/blob/a8a5afe/src/commands/init.rs), [add.rs](https://github.com/railwayapp/cli/blob/a8a5afe/src/commands/add.rs), [project.rs](https://github.com/railwayapp/cli/blob/a8a5afe/src/commands/project.rs), [list.rs](https://github.com/railwayapp/cli/blob/a8a5afe/src/commands/list.rs)

package/.agents/skills/use-railway/scripts/railway-api.sh

@@ -0,0 +1,41 @@
+#!/usr/bin/env bash
+# Railway GraphQL API helper
+# Usage: railway-api.sh '<graphql-query>' ['<variables-json>']
+
+set -e
+
+if ! command -v jq &>/dev/null; then
+  echo '{"error": "jq not installed. Install with: brew install jq"}'
+  exit 1
+fi
+
+CONFIG_FILE="$HOME/.railway/config.json"
+
+if [[ ! -f "$CONFIG_FILE" ]]; then
+  echo '{"error": "Railway config not found. Run: railway login"}'
+  exit 1
+fi
+
+TOKEN=$(jq -r '.user.token' "$CONFIG_FILE")
+
+if [[ -z "$TOKEN" || "$TOKEN" == "null" ]]; then
+  echo '{"error": "No Railway token found. Run: railway login"}'
+  exit 1
+fi
+
+if [[ -z "$1" ]]; then
+  echo '{"error": "No query provided"}'
+  exit 1
+fi
+
+# Build payload with query and optional variables
+if [[ -n "$2" ]]; then
+  PAYLOAD=$(jq -n --arg q "$1" --argjson v "$2" '{query: $q, variables: $v}')
+else
+  PAYLOAD=$(jq -n --arg q "$1" '{query: $q}')
+fi
+
+curl -s https://backboard.railway.com/graphql/v2 \
+  -H "Authorization: Bearer $TOKEN" \
+  -H "Content-Type: application/json" \
+  -d "$PAYLOAD"