MoonClerk
Read MoonClerk payment forms, customers (plans) and payments through the MoonClerk read-only API.
About
MoonClerk ships in the w6w first-party pack. It declares 6 actions, 3 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.moonclerk- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Commerce & Payments
Overview
MoonClerk builds payment forms on top of Stripe: one-time checkouts, subscriptions and installment plans, with a hosted page where a customer manages their own plan. This app connects a workflow to MoonClerk’s read-only REST API with an API key.
A workflow can list and read payment forms with their volume and checkout counts; list and read customers (what the MoonClerk dashboard calls plans) with their subscription, plan amount, next payment date, discount, custom-field answers and self-service management URL, filtered by form, checkout date, next-payment date or subscription status; and list and read payments, filtered by form, customer, charge date or status, with the Stripe fee, refunded amount and Stripe references. Nothing can be created, changed or cancelled: MoonClerk’s API is read-only.
MoonClerk answers a bad key with a plain-text HTTP 401 HTTP Token: Access denied.; this app reads that body. Health checks verify the key and whether the API answers.
Build with MoonClerk
Three routes to the same 6 actions. The Workflow tab is generated from MoonClerk'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 Customer
customer-get Fetch one customer (MoonClerk 'Plan') by ID, with its subscription, plan, discount, checkout and custom-field answers.
List Customers
customer-list List customers (MoonClerk 'Plans') with subscription, plan, discount and custom-field answers, filtered by form, checkout date, next payment date or subscription status.
List Forms
form-list List the account's payment forms with their currency, payment volume and successful checkout count.
Get Payment
payment-get Fetch one payment by ID, with amount, Stripe fee, refunded amount, Stripe references, coupon and custom-field answers.
List Payments
payment-list List payments with amount, Stripe fee, refunded amount and Stripe references, filtered by form, customer, charge date or status.
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 MoonClerk's real ids.
{
"manifestVersion": "2",
"name": "moonclerk-example",
"steps": [
{
"id": "customer-get",
"uses": {
"app": "io.w6w.moonclerk",
"action": "customer-get",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"customerId": "<customerId>"
}
}
]
}Here are some of the things you can do
-
Get Customer
readcustomer-get -
List Customers
searchcustomer-list -
Get Form
readform-get -
List Forms
searchform-list -
Get Payment
readpayment-get
+1 more action 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 MoonClerk, 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 MoonClerk. 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: "customer-get",
payload: {
customerId: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action customer-get --payload '{"customerId":"<value>"}'Give an AI agent MoonClerk — without giving it MoonClerk'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.moonclerk#customer-get",
"input": {
"customerId": "<customerId>"
}
}
}
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 MoonClerk 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
MoonClerk'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. MoonClerk itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
MoonClerk declares its own checks, so its health is a property of the app rather than something the host guesses at.
MoonClerk platform status
API reachable
Unauthenticated GET /forms. MoonClerk's `Access denied` 401 passes: it proves the application is answering.