One API, one module.
Start from public API documentation and one synthetic example. Choose one trigger or action rather than hiding uncertainty inside a broad app build.
bounded input → outputMake / custom app proofV1 / SYNTHETIC
Build the module.
Prove the boundary.
A local workbench for taking one public API from idea to a bounded Make custom-app contract: definition, auth choice, sample input/output, and named stops for bad responses.
Browser-local fixtures only. No credentials, client data, API calls, or Make account access are used by this page.
app.contract / v1 PUBLIC PROOF
01
App definitionname + version + scope
READY02
Auth boundarykey or OAuth / buyer choice
DECLARED03
One moduleaction / request / response
BOUNDED04
Failure policyempty / retry / review
HOLDABLEproof boundaryno live call
The useful first unit
A custom app is a contract, not a prompt.
Claude Code can accelerate scaffolding. Make still needs a valid app definition, an explicit auth choice, module input/output mapping, and a failure policy that a human can accept. This page shows that boundary with synthetic values only.
Run the contract
One module. Four honest readbacks.
Choose a fixture, run it locally, and inspect the exact decision. “PASS” means the synthetic shape is internally consistent; “HOLD” means the safe result is to stop before a live module call.
Module fixturecreate-record.json
Synthetic values are generated in this browser. They are never sent to Make, the API, or RomeoApps.
Acceptance readbackREADY
READY
Select a case, then run the contract.
The local evidence sheet will name the next safe owner without contacting a live service.
- module
- createRecord
- response shape
- object
- next owner
- Not assigned
01definitionvalid app shape
02authdeclared, not supplied
03moduleone bounded action
04decisionaccept or hold
What the first pass covers
Make the smallest safe promise visible.
Show the contract.
Record the app definition, auth choice, field mapping, sample response, setup notes, and the exact cases that stop or retry.
fixture → readbackHold what is not proven.
No credentials, private data, live send, production guarantee, or unrelated modules belong in the first unit before fit and acceptance are written.
unknown → review ownerA bounded paid starting point
One public API. Two business days. A handoff someone can accept.
USD 350 / fixed first unit
Async after fit is confirmed. Payment and any protected access happen through the agreed written route; this proof page needs neither.
Send a safe brief ↗- 01Share public docs.
Tell me the first trigger or action and include one synthetic example.
- 02Confirm the boundary.
I reply with the module scope, auth assumption, evidence, and acceptance owner.
- 03Receive the first unit.
Get the importable app package or equivalent source handoff plus setup and failure-path notes.
No invented client story
Inspect the method. Then bring the real API.
This is RomeoApps-owned synthetic proof, not a claim that a buyer's private app is already built. The next step is a fit check against the public docs.