Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.constants.io/llms.txt

Use this file to discover all available pages before exploring further.

Create Tools from Anything

Bring your code however you want — Constants handles the rest:
https://github.com/your-org/scripts/blob/main/process_data.py
Constants fetches the repo, analyzes the script, and generates the tool automatically. You can also scan entire repos to discover multiple tools at once.

Typed Inputs & Outputs

Every tool gets a defined interface — typed input fields and structured outputs. This interface drives the web UI form, the API contract, and the MCP tool definition, keeping them all in sync:
  • Input types: Text, numbers, files, directories, arrays — with validation
  • Output types: Text, numbers, files, JSON — rendered automatically in the UI
  • Credentials: Declare what secrets a tool needs; they’re resolved and injected at runtime
  • Compute tier: Choose resource allocation from small to GPU

Secure Sandbox Execution

Every tool runs in an isolated sandbox:
  • Fresh environment per execution — no state leaks between runs
  • Resource tiers from lightweight scripts to GPU-powered ML inference
  • Pre-installed packages including pandas, numpy, scipy, cloud SDKs, and ffmpeg
  • Credential protection — secrets are encrypted and injected at runtime, never exposed to users or the sandbox directly
  • File handling — upload inputs, download output artifacts

Run History & Artifacts

Every execution is recorded:
FieldDescription
InputsThe exact parameters and files provided
StatusRunning, completed, failed, cancelled
LogsReal-time streaming stdout/stderr
TimingStart time and duration
ArtifactsOutput files — downloadable from UI or API
TriggerWho ran it (UI, Slack, API, agent)
Replay any run with the same inputs, or use the history to debug failures.

Built-in Utilities

Tools have access to pre-built Python utilities for common tasks:
CategoryWhat You Get
Search & ScrapeWeb search, website scraping
LLMCall language models, extract structured data
Cloud StorageGCP Storage, Firestore, BigQuery, Spanner, AWS S3
MediaImage generation, speech-to-text, text-to-speech, video/audio processing
FilesFile uploads, PDF processing
DataLinkedIn data, YouTube downloads
These are loaded automatically based on the tool’s needs — no manual configuration required.

Run from Slack

Install the Constants bot in your Slack workspace and mention it to run tools:
@Constants process this CSV with the report generator
The bot reads thread context for multi-turn interactions, executes the tool in a secure sandbox, and posts results back — all without leaving Slack.

Agent Chat

Constants includes a built-in AI assistant that can:
  • Discover your tools and understand what they do
  • Execute tools and return results
  • Chain multiple tools into multi-step workflows
  • Accept file attachments and route them to the right tool

REST API & MCP

Every tool is automatically available as:
  • REST APIPOST /v1/run/[toolName] for programmatic access
  • MCP endpoint — standard Model Context Protocol for AI agent integration
Both use the same execution path as the UI — same sandbox, same credentials, same logging. See the API Reference for details.

Teams & Organizations

Create team workspaces with shared tools, credentials, and usage quotas. Personal workspaces are auto-created for individual use.
Roles: owner, admin, member, viewer — enforced on every operation. Invite teammates by email.
Per-workspace limits on LLM, search, scrape, image, and media operations. Configurable per plan.
Workspace-level credentials shared across team members, with personal credentials available for individual use.

Security

LayerHow It Works
Sandbox isolationEach run in its own container with no access to other runs or host systems
Credential encryptionSecrets encrypted at rest and injected securely at runtime
API key scopingKeys have configurable permission scopes with revocation support
Access controlOwnership, sharing, and role verification on every operation
Audit trailEvery run logged with full context — who triggered it, with what credentials, and what happened

Conversation Mode

Refine your tools through natural language:
  • Request changes: “Make the filter case-insensitive”
  • Debug failures: “Why did the last run fail?”
  • Add features: “Add an option to output Excel format”
  • Get explanations: “What does this tool do with the input file?”

What’s Next?

GitHub Integration

Import scripts and scan repos for tool candidates

API Reference

REST API, MCP, and Slack bot access