Tremendous
Send gift cards, prepaid cards, cash and donations, and manage the orders, rewards, products and campaigns behind them, via the Tremendous API.
About
Tremendous ships in the w6w first-party pack. It declares 14 actions, 3 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.tremendous- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Commerce & Payments · Human Resources
Overview
Tremendous is a payouts and incentives API: gift cards, prepaid Visa/Mastercard, cash (PayPal, Venmo, ACH, international bank transfer) and charitable donations, sent one at a time or in bulk to employees, customers, survey respondents and research participants.
Every reward is sent by creating an Order, which either names a specific catalog product (a single Amazon.com gift card) or a Campaign that lets the recipient pick from a curated set. Orders are idempotent: supplying the same external_id twice returns the original order instead of paying twice, which is the retry-safety this app leans on for every money-moving action. Rewards created by an order can be listed, resent after a failed delivery, canceled before redemption, or turned back into a redemption link for a channel Tremendous doesn’t deliver to directly (Slack, an in-app notification, a support ticket reply).
The Product and Campaign catalogs are read-only lookups a workflow queries before building an order — which gift cards are available in a country/currency, what a campaign’s curated set looks like — and Funding Sources reports what’s available to pay with, including the account’s own USD balance.
Health checks track Tremendous’s own status page, the API credential’s liveness, and the account balance’s remaining headroom, so a workflow that sends rewards on a schedule finds out about an empty balance from a health check rather than from a batch of failed orders.
Build with Tremendous
Three routes to the same 14 actions. The Workflow tab is generated from Tremendous's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Get Funding Source
funding-source-get Retrieve one funding source by ID, or the keyword BALANCE or INVOICE.
Create Order (Send Reward)
order-create Send a gift card, prepaid card, cash payout or donation to one recipient.
List Orders
order-list List orders, newest first, optionally filtered by campaign, external ID or date.
List Products
product-list List available reward products (gift cards, prepaid cards, cash, donations).
Cancel Reward
reward-cancel Cancel a reward with a delivery failure and refund its cost. Redeemed rewards cannot be canceled.
Generate Reward Link
reward-generate-link Generate a fresh redemption link for a reward. Deliver it yourself.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Tremendous's real ids.
{
"manifestVersion": "2",
"name": "tremendous-example",
"steps": [
{
"id": "campaign-get",
"uses": {
"app": "io.w6w.tremendous",
"action": "campaign-get",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"id": "<id>"
}
}
]
}Here are some of the things you can do
-
Get Campaign
readcampaign-get -
List Campaigns
searchcampaign-list -
Get Funding Source
readfunding-source-get -
List Funding Sources
searchfunding-source-list -
Create Order (Send Reward)
performorder-create
+9 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Tremendous, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Tremendous. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "campaign-get",
payload: {
id: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action campaign-get --payload '{"id":"<value>"}'Give an AI agent Tremendous — without giving it Tremendous's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.tremendous#campaign-get",
"input": {
"id": "<id>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Tremendous connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Tremendous's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Tremendous itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Tremendous declares its own checks, so its health is a property of the app rather than something the host guesses at.
Tremendous platform status
Page-level status from status.tremendous.com, plus any active incidents.
Balance headroom
Remaining Tremendous account balance, read from GET /funding_sources/BALANCE.