TinTinWorkflows
GitHubSign in

Would a careful buyer hand over a card here?

Run it before launch or after a signup walkthrough. Tin reads your public pages the way a careful buyer would, compares what the site promises with what the project knows, and gives a PASS, FAIL or UNVERIFIED verdict from fixed rules, with the fixes ranked.

Try in browser →
codex mcp add tin --url https://app.tin.computer/mcp
Checkout trust check
qa.buyer_trust
outputreports/BUYER_TRUST.md
guardrailPublic GET requests only. It never signs in, submits forms, changes your site or claims CVE coverage.
needsA public HTTPS product URL. A signup walkthrough and feature map make the check more complete.
required inputsproduct_url
optional inputsdepth, notes
sourcegithub.com/tin-computer/tin →

What the workflow does.The same steps, every run.

A Tin workflow is a repeatable job: declared inputs, a bounded run and a defined output.

  1. 01Reads the newest signup walkthrough for the checkout path and price line, so signup is never walked again.
  2. 02Fetches public pages with GET and HEAD only: pricing, contact, refund and terms, depending on depth.
  3. 03Compares what the site tells a buyer with the plans, prices and refund terms the project records.
  4. 04Gives a verdict from fixed rules, so two runs on the same evidence agree, and ranks the fixes.
ask your agent

Check whether a careful buyer would trust our checkout, and rank what to fix first.

What every workflowcomes with.

Battle tested on real products

These are the workflows we run for real companies. Claw Messenger went from about $45 to $2,105 in monthly revenue in 124 days on them. Each one has declared inputs, bounded execution and tests, and anything public waits for your review.

See the case study →

Open source: read it, fork it, self-host it

Apache 2.0. Every workflow is a folder in the repository: the steps it runs, the data it reads and what it is allowed to do. Change it, or run the whole system on your own machine.

Open the repo →

Runs on the agent that already knows your product

The fixes are usually small: a refund page, a contact address, a price that disagrees with the code. Your agent can make them in the repository right away.

All workflows →

Runs well with.Workflows that feed this one, or follow it.

Signup walkthroughqa.signup_walkthroughFeature-by-feature auditqa.product_auditTechnical SEO fixes as one PRorganic.technical_fix

Questions.

Is this a security scan?

No. It is a trust check for conversion, not a penetration test, and it does not claim CVE coverage.

Does it enter a card or create an account?

No. What lies behind signup comes from the signup walkthrough's report or is left unverified.

Is Tin really open source?

Yes. Tin is licensed under Apache 2.0 and the source is at github.com/tin-computer/tin. You can read every workflow, change it, and self-host the whole system.

Which coding agents can run Tin workflows?

Any agent that speaks MCP, including Claude Code, Codex and Cursor. There is also an API, and the same projects run in the browser at app.tin.computer.

Why run marketing from a coding agent?

Because it already knows your product. It has the repository open, so it fills workflow inputs accurately, reviews output against what the product really does, and can act on the results in the same session.

Add Tin to your coding agent.It takes one command.

Try in browser →
codex mcp add tin --url https://app.tin.computer/mcp