Do you store the answers I give in the interview?

No. There is no database attached to this site at all. The nine answers become nine characters in the address bar, which is how a manifest survives a reload and how you can paste one to somebody else. Close the tab and there is nothing left anywhere.

Do I hand over my GitHub, Stripe or Google credentials?

Never, and there is nowhere here to put them. This site produces the list and the exact scope each service wants. The connections themselves are made by your assistant on your own machine, against your own accounts. A site that holds other people's tokens is a target, and this one has deliberately made itself a boring one.

What actually is a manifest?

One page listing every account your build needs, why this particular build needs it, the exact permission to grant, the real free allowance, and what breaks if you skip it. Plus the forty-six checks the finished thing has to pass. It is written to be handed straight to an assistant without editing.

What if I do not have an AI assistant?

The list is still the list. Answer 'me, by hand' to the last question and nothing about the output changes except that no model key appears on it. Plenty of people use this to plan a build they intend to write themselves.

Can I connect Jarvis, Claude Code, or Cursor?

Not yet, and the assistant page says so rather than showing a button that does nothing. Today you copy the manifest and paste it into whatever you already use, which works with every assistant that exists. The direct bridge is designed and not built.

Are the free-tier figures reliable?

They were read from each vendor's own pricing page on the date shown beside them, and they will drift. That is why the date is printed rather than hidden. If you find one that has moved, say which and it gets corrected in the catalogue for everyone.

Why does answering 'people sign in' change so much?

Because it is the answer that quietly commits you to the most. Sign-in means a database, which means row-level security. It means session cookies that have to be HttpOnly, Secure and scoped. It means password hashing with Argon2id and a rate limit checked before the credential, not after. One question, and about a week of obligations.

Answered plainly

Questions about connecting accounts

Seven questions, including the two that people are right to be suspicious about.

01: No. There is no database attached to this site at all. The nine answers become nine characters in the address bar, which is how a manifest survives a reload and how you can paste one to somebody else. Close the tab and there is nothing left anywhere.
02: Never, and there is nowhere here to put them. This site produces the list and the exact scope each service wants. The connections themselves are made by your assistant on your own machine, against your own accounts. A site that holds other people's tokens is a target, and this one has deliberately made itself a boring one.
03: One page listing every account your build needs, why this particular build needs it, the exact permission to grant, the real free allowance, and what breaks if you skip it. Plus the forty-six checks the finished thing has to pass. It is written to be handed straight to an assistant without editing.
04: The list is still the list. Answer 'me, by hand' to the last question and nothing about the output changes except that no model key appears on it. Plenty of people use this to plan a build they intend to write themselves.
05: Not yet, and the assistant page says so rather than showing a button that does nothing. Today you copy the manifest and paste it into whatever you already use, which works with every assistant that exists. The direct bridge is designed and not built.
06: They were read from each vendor's own pricing page on the date shown beside them, and they will drift. That is why the date is printed rather than hidden. If you find one that has moved, say which and it gets corrected in the catalogue for everyone.
07: Because it is the answer that quietly commits you to the most. Sign-in means a database, which means row-level security. It means session cookies that have to be HttpOnly, Secure and scoped. It means password hashing with Argon2id and a rate limit checked before the credential, not after. One question, and about a week of obligations.

Still unanswered

Ask the actual question.

Every message gets a reply within two working days. If the answer belongs on this page, it ends up here.

Contact →

Or skip ahead

Four minutes gets you the list.

The interview explains each question as it asks it, which answers most of these in passing.

Describe what you are building →