OneSimpleApi
A toolbox of small utility APIs: page metadata, screenshots, PDFs, QR codes, email validation, URL expansion, and currency conversion.
About
OneSimpleApi ships in the w6w first-party pack. It declares 7 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.onesimpleapi- Version
- 0.1.2
- Author
- w6w
- Licence
- MIT
- Categories
- Developer Tools
Overview
OneSimpleApi brings a toolbox of small utility operations into a workflow: fetching a web page’s metadata, taking a screenshot, generating a PDF or QR code, validating an email address, expanding a shortened URL, and converting between currencies. Each action wraps one focused, well-defined utility endpoint rather than a broad product surface, making this a good fit for the small one-off lookups and conversions that come up inside a larger workflow.
The screenshot, PDF and QR code actions each generate a hosted resource on the vendor’s own CDN and are safe to retry — the same inputs reuse a previously generated result rather than creating duplicates. The remaining actions are simple, side-effect-free reads: checking a page’s metadata, validating an email format, resolving a shortened link back to its destination, or converting a currency amount at current rates.
This app covers a focused subset of OneSimpleApi’s documented endpoints, chosen to match the small-utility use case rather than the vendor’s larger, more specialized surfaces like image manipulation or link shortening.
Build with OneSimpleApi
Three routes to the same 7 actions. The Workflow tab is generated from OneSimpleApi'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.
Convert Currency
convert-currency Convert a value from one currency to another using current exchange rates.
Get Page Info
get-page-info Retrieve a webpage's title, meta tags, Twitter Card, and Open Graph data.
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 OneSimpleApi's real ids.
{
"manifestVersion": "2",
"name": "onesimpleapi-example",
"steps": [
{
"id": "convert-currency",
"uses": {
"app": "io.w6w.onesimpleapi",
"action": "convert-currency",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"toCurrency": "<toCurrency>"
}
}
]
}Here are some of the things you can do
-
Convert Currency
readconvert-currency -
Create PDF
performcreate-pdf -
Expand URL
readexpand-url -
Generate QR Code
performgenerate-qr-code -
Get Page Info
readget-page-info
+2 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 OneSimpleApi, 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 OneSimpleApi. 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: "create-pdf",
payload: {
// url: "<value>",
// html: "<value>",
// page: "<value>",
// background: "<value>",
// force: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action create-pdf --payload '{}'Give an AI agent OneSimpleApi — without giving it OneSimpleApi'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.onesimpleapi#convert-currency",
"input": {
"toCurrency": "<toCurrency>"
}
}
}
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 OneSimpleApi 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
OneSimpleApi'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. OneSimpleApi itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
OneSimpleApi declares its own checks, so its health is a property of the app rather than something the host guesses at.
OneSimpleApi platform status
No machine-readable status surface: onesimpleapi.com publishes no status page.
API usage headroom
Not exposed via the API: usage percentage is dashboard-only (Inertia page props), with no documented API endpoint or response header.