Agents without pre-built tools

Most agents can act only through a fixed catalog of tools. Every supported action has to be anticipated, mapped, and deployed before the agent can use it. superglue removes that constraint: connect a system once, give the agent access, and let it retrieve the relevant system context and assemble the required read or write operation at runtime.

!

The connection defines how to interact with a service. superglue resolves its secrets only when the operation runs, so the agent works with secret names rather than secret values.

What this unlocks

A user can ask “get my last five invoices” and then “update the billing email for customer X.” The agent can execute both requests through the same system without someone pre-building two separate tools.

Inspect every operation

Each execution creates a run record with the generated configuration, systems called, results, timing, and any errors.

Keep secrets protected

API tokens, OAuth tokens, and passwords remain in superglue connections and are resolved only during execution.

Control agent access

API-key restrictions, roles, and direct sharing determine which tools and connections an agent can use.

How it works

Your agent uses the superglue CLI (sg) and the superglue skill. The skill provides the command, authentication, and configuration context needed to work with superglue safely.

1. Discover available systems

   sg system list

2. Consult provider documentation

   The agent checks the provider’s documentation for endpoints, authentication, pagination, and response shapes.

3. Execute the required operation

   The agent can run an inline configuration without first saving a permanent tool.

   sg tool run --config '{
     "id": "get-invoices",
     "instruction": "Fetch recent Stripe invoices for a customer",
     "steps": [{
       "id": "list-invoices",
       "config": {
         "systemId": "stripe",
         "url": "https://api.stripe.com/v1/invoices?customer=<<customerId>>&limit=5",
         "method": "GET",
         "headers": {"Authorization": "Bearer <<stripe_api_key>>"}
       }
     }]
   }' --payload '{"customerId": "cus_abc123"}'

4. Return and monitor the result

   The agent returns the result to the user, while superglue records the run for monitoring and failure investigation.

Setup

Follow CLI + Skills to install and authenticate the CLI and add the superglue skill to your agent. Then create the connections the agent should use and grant only the access it needs.