Agents

Agents CLI

The CLI is the fastest way to validate agent payloads and debug integration behavior before wiring tools into your orchestrator.

These commands use the read API and submit API. Make sure you have an API key before starting.

Setup

Install the CLI and authenticate once. The key is saved to your config and reused across sessions.

1. Install the CLI

npm i -g @theodevs/nativeform-cli

2. Log in

nativeform login

This opens the API keys page in your browser. Create or copy a key, then paste it when prompted. The key is saved locally and used for all subsequent commands.

Alternative: environment variables

For CI or when you prefer not to persist a config, set NATIVEFORM_API_KEY in your environment. The CLI also accepts --token per command.

Commands

Use reproducible commands for test fixtures and incident response. Curl examples below require NATIVEFORM_API_KEY; the nativeform CLI uses the key from login.

GET/api/forms

List forms

GET/api/forms/{formId}/responses

List responses

POST/api/forms/{formId}/responses

Submit response

Safety

CLI convenience should not weaken your key hygiene.

Never commit shell history

Avoid committing exported shell history that includes plaintext API keys. Add .bash_history and .zsh_history to your global gitignore.

Short-lived terminal sessions

Use short-lived terminal sessions when handling production credentials. Close the session when done.

Prefer environment variables

Always use environment variables over passing keys inline in command arguments. Inline keys appear in process lists.

Rotate after sharing

Rotate keys after sharing debugging sessions, screen recordings, or terminal replays that may have captured credentials.

Security Warning

Never use production API keys in shared terminal sessions or CI logs. Create dedicated short-lived keys for testing.