PAYTOCOMMITStatus
StatusLoading service health
Preparing live service states, incidents, and maintenance windows.
Preparing live service states, incidents, and maintenance windows.
Search getting started, commitment markets, funding, payouts, consent, and enterprise access from one place.
Results update while you type across the full FAQ library.
The page stays focused on the questions people ask before they join, fund, integrate, or grant identity-backed consent.
Jump from the FAQ into the docs host or the full help library when you need the next step.
Start with the basics, unlock funding, and understand how the first commitment works.
PayToCommit is a commitment market where you stake on your own goal, submit proof before the deadline, and get paid when you finish under the published rules.
Every market shows the goal, join window, proof mode, result timing, and payout rules before you commit.
Use signup to create your account with email and password, or continue with Google, Apple, or Discord where available.
Once your account is live, you can browse markets, join Spark, save drafts, and move into identity verification only when you are ready to fund your wallet or place a live stake.
Yes. Guests can read the board, open market detail, move through Fractal Markets, and watch live pulse graphs without a login wall.
The account wall appears only when you try to lock a live stake, save a protected action, or open a direct Galactus conversation.
Identity verification is not required to create an account. It becomes required when you try to fund the wallet or place a live stake because wallet cash, payouts, and proof-linked settlements run through verified accounts only.
PayToCommit uses Stripe Identity to confirm legal identity, government ID, and any required live capture steps before funding opens.
Generate unlocks after you complete at least one verified commitment within the last 30 days.
Until then, the board stays in Search mode so you can browse live markets, join existing goals, and see how proof and settlement work before drafting a new one.
Quickstart shows the shortest path from signup to your first verified completed commitment: verify email, pick a commitment, deposit your first $10 when you are ready to stake, and finish it cleanly.
It also shows what still unlocks later, including Generate and the rest of the Galactus access window.
Invite rewards post only after the invited user signs up, funds the wallet, places the first live stake, and completes that first verified commitment.
When that verified result posts, $10 can release to the invited user and $10 can release to the referrer. Before that final verified finish, the tracker stays in progress instead of paying early.
Quickstart is designed to guide the account without interrupting market discovery. It stays visible on the board and profile route once the email is confirmed, but it does not block the rest of the product.
The dedicated quickstart route is still available when you want the full checklist and the longer enterprise setup path.
Galactus unlocks only after one verified completed commitment within the last 30 days. The same rule applies to generation, docs AI, and the direct Galactus support or sales conversation.
Public docs and public help pages stay readable without Galactus, and support or enterprise intake can still start without the direct AI conversation.
If you try to use a locked Galactus surface anyway, the product responds with the same direct rule and points you back to the next step that restores access.
Read how dates, proof, nested markets, and visible totals work before you join.
Start with the category, deadline, proof mode, and stake band. If the rules fit the goal you want to finish, you can commit from the board or the full market page.
Markets that are still very new can show activity without a full visible pool total until they pass the published visibility threshold.
Very new markets can keep the full pooled total hidden until they pass the published reveal threshold. This keeps the opening phase readable without overstating what is already public.
The market can still show timing, proof mode, stake band, and controlled activity signals before the full total is revealed.
Each market has a start window, a join window, a proof deadline, and a result window. You can only join while the join window is open.
PayToCommit AI drafts these dates when a new market is created, but the dates do not go live until the creator explicitly opens the market.
Fractal Markets are nested goal tracks inside a parent commitment market. They let a broad goal break into smaller tracked paths, each with its own proof view and timing.
The parent market stays the main settlement container, while the fractal tracks show the progress structure inside it.
Open the market before the proof window closes and submit the proof requested in the rules. Markets can require text, image, video, or higher-trust native capture depending on the goal.
If a market needs stronger proof capture, PayToCommit routes you into the required capture flow before the submission window closes. STP-sensitive proof submission is handled through the mobile app, not desktop upload alone.
Desktop is available for browsing, funding, joining, and managing positions. Some markets still require mobile proof because the rules need device-backed capture and timed challenge-response checks that the browser alone cannot provide.
The market tells you which proof mode it needs before you commit, so the mobile requirement is clear before funds are at risk.
The desktop session keeps the stake locked and opens a handoff state that says your funds are already staked and proof continues on mobile.
From there you can scan the QR code or use the smart link to continue the same market and stake on your phone without losing the session context.
PayToCommit AI rejects drafts that are harmful, illegal, abusive, or not verifiable enough to settle cleanly.
If a draft cannot be verified by the published proof rules, the system explains why and asks for a safer or more concrete version instead of opening the market.
Some markets require stronger capture than a desktop browser can provide. Those markets use mobile proof so the platform can run device-backed capture, timed challenge-response, and the right proof checks for that market.
You can still browse, fund, join, and manage markets on desktop. The rules tell you before you commit if proof must be submitted through the mobile app.
Know how funding works, when cash posts, and how completed markets pay out.
Once your identity is verified, Add Funds routes you into the dedicated funding screen where you can choose Apple Pay, Google Pay, debit card, or ACH and wire.
Funding availability depends on device and processor eligibility. ACH and wire use a $1,000 minimum and a flat $20 fee.
Sovereign Spark is the 5% infrastructure fee attached to each commitment stake. It covers the verification and AI systems used to run the market.
It is separate from the Settlement Tax, which is the platform capture from the failed or fraudulent side of a market.
Completed entrants recover their qualifying stake and receive their share of the failed side under the market rules after fees.
Wallet cash posts after settlement is final and any published proof or challenge windows are closed.
Early Release closes a live commitment before the deadline and applies the published 5% pre-deadline forfeiture of the original stake.
The product shows the exact return amount before confirmation so you can see the effect before you leave the market.
You can cash out posted wallet balance after identity verification is complete and the relevant funding or settlement events have posted.
Pending funding, pending settlements, and active holds do not count as spendable or withdrawable cash until they clear.
Protected access, Human Reliability API coverage, and the enterprise billing model.
The Human Reliability API is a consent-gated enterprise API that returns protected reliability signals derived from verified commitment history.
Approved scopes can include current HRS standing, live trend direction, and identity-backed matching to the consenting person's legal identity. It is built for banks, enterprises, platforms, and other organizations that need auditable access to user-approved reliability data.
No. New accounts start without a reliability score. The score begins building only after verified commitment history starts to accumulate.
The score can rise, flatten, dip, and recover over time. Enterprise views can use that trend only within the user's granted consent scope.
Yes. Protected reliability lookups require active user consent, a scoped enterprise key, and a declared access purpose.
There is no open legal-name lookup and no unrestricted bulk search across user records. Legal-name-backed matching becomes available only when the user granted that identity scope to the approved integration.
Yes, but only when you grant the identity scope to that approved organization for the declared purpose. Without that scope, the organization cannot match the protected record to your legal identity.
That consent makes your earned record usable for that approved review. It does not create a stronger score or turn the API into open people search.
With the granted scope, an approved enterprise can review the protected reliability record tied to the consenting person's legal identity, current HRS standing, and the live trend history allowed by that consent.
Without that scope, the enterprise cannot see legal-name-backed matching and cannot read outside the remaining granted access window.
Consent does not manufacture points or inflate the score on its own. The score still comes from verified commitment history.
What consent can do is make that verified record available to approved organizations that the user wants to work with, which can open more opportunities without changing how the score is earned.
Consent lets an approved organization review the verified record you already earned instead of seeing no protected reliability history at all.
That can make your live HRS history, recovery pattern, and legal-name-backed match usable for approved decisions when you want that record considered. It does not manufacture points or override the way the score is actually earned.
Yes, but only when the user granted the identity scope to that approved integration. Without that scope, the protected record cannot be matched to the user's legal identity.
With the granted scope, approved teams can review current HRS, live trend direction, and the protected history allowed by that consent.
Enterprise billing is usage-based. Protected calls, audit coverage, consent-scoped access, and live HRS dashboard usage determine billable usage.
API keys are scoped, logged, and tied to enterprise accounts so access stays auditable from request through response.
Yes, within the granted consent scope. Approved enterprise views can follow the protected HRS trend, including rises, plateaus, recoveries, and the latest verified changes tied to that record.
That view is still scoped, logged, and purpose-bound. It is not an unrestricted history feed across every user on the platform.
Enterprise and small-business teams start from the sales route, where the organization submits its use case, expected request volume, consent requirements, legal-identity scope needs, and contact details.
Public enterprise docs stay readable without sign-in. Direct Galactus-led sales access follows the same recent verified-completion rule used for other protected AI features.
No. The Human Reliability API is built for enterprises, platforms, and smaller businesses that need consent-backed reliability review for real decisions.
The application flow still asks for your request band, use case, and scope so Galactus can qualify the right billing and integration path before protected access opens.
Some organizations need to know that the protected reliability record belongs to the exact person they are reviewing. That is why identity-backed matching exists as a separate consent scope.
Without that granted scope, the organization cannot tie the record to the user's legal identity. With that scope, it can review the same earned reliability history for the approved purpose under that person's legal name.
No. Human Reliability is a consent-based performance signal built from verified commitment history, not a replacement for regulated credit reporting.
Organizations should treat it as a distinct reliability signal and use it only within the consent scope granted by the user.
How social posting, help routes, and Galactus access work across the network.
Galactus runs on GPT-5.4 through the OpenAI Responses API for reasoning, drafting, support, docs, and sales.
If a workflow includes uploaded video, Twelve Labs can analyze the footage first and return structured video context that Galactus uses in the same thread.
Spark is the feed, reply, and reaction layer attached to markets. Ruzomi is the wider social-network experience built around those same commitment channels.
Joined commitment markets become your channels inside Ruzomi, which replaces generic server lists with the markets you actually joined.
Public docs, FAQ, and help pages stay open so anyone can understand the platform. Direct Galactus conversations are protected features and require one verified completed commitment inside the active 30-day window.
Support intake and enterprise request forms stay reachable even before that direct Galactus window opens.
If that requirement is missing, the product tells you exactly what step unlocks access instead of opening a half-working chat: finish one verified commitment and return inside the 30-day window.
That same automatic answer appears across docs, support, sales, and market generation so the access rule stays consistent everywhere Galactus appears.
No. Guests can read public activity, but posting, reacting, replying, voting, and idea creation all require a signed-in account.
The product does not create fake placeholder posting identities for unsigned visitors.
No. Contact sync is optional. The mobile app asks for permission before reading contacts and lets you keep that access off if you do not want to use it.
If you do grant access, the app can show which contacts are already on the platform and which people can receive a direct invite link.
PayToCommit keeps browsing open so guests can read markets, inspect Fractal Markets, and watch pulse graphs before any account wall appears.
The account wall appears only when you try to lock a live stake, save another protected action, or open a direct Galactus conversation. That keeps discovery open while still capturing the account and the exact market intent before money moves.
The desktop session keeps the stake locked and opens a handoff state that says your funds are already staked and proof continues on mobile.
From there you can scan the QR code or use the smart link to continue on your phone without losing the market, stake amount, or next proof step.
Result artifacts are the branded cards that appear after a market resolves. Completed results can reveal a victory artifact and missed results can reveal a forfeiture artifact.
If you were offline when the result posted, the artifact can appear on the next login so the outcome is still visible and shareable.