tightly.io valid
Tightly help centre
The knowledge base behind Ask Tightly: one article per concept, page, act and refusal of the platform.
- Authority
- 45 reach 0 · trust 5 · quality 25 · freshness 15
- Tier
- listed
- llms.txt
- https://docs.tightly.io/help/llms.txt
- llms-full.txt
- https://docs.tightly.io/help/llms-full.txt
- Sections
- 15
- Links
- 143
- Size
- 29969 bytes
- Country
- — Publisher location unknown; CDN address excluded
- Country evidence
- No published address evidence collected yet
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-26T02:12:45.489Z
- Last checked
- 2026-10-26T02:12:48.031Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-26T02:12:45.495Z. Cached copy · Source on tightly.io
# Tightly help centre
> The knowledge base behind Ask Tightly: one article per concept, page, act and refusal of the platform.
## Commitments
- [A colourway the style is not offered in](https://docs.tightly.io/help/commitments/a-colourway-the-style-is-not-offered-in): Where a colour split names a colourway the style does not come in:
- [A size split that does not total](https://docs.tightly.io/help/commitments/a-size-split-that-does-not-total): Where the shares of a size split do not add up to the whole buy:
- [Decline a scenario](https://docs.tightly.io/help/commitments/act-decline-a-scenario): Decline a scenario records that a scenario was not taken, with a stated reason
- [Set a colour split](https://docs.tightly.io/help/commitments/act-set-a-colour-split): Set a colour split records how one style's buy divides across its colourways, keyed on your own colourway names: a share per colourway in basis points, summing to ten thousand, on one commitment
- [Set a size split](https://docs.tightly.io/help/commitments/act-set-a-size-split): Set a size split records how one style's buy divides across its sizes: a share per size in basis points, summing to ten thousand, on one commitment
- [Set a worked depth](https://docs.tightly.io/help/commitments/act-set-a-worked-depth): Set a worked depth records how many units of one style a person decided to buy on one commitment: one row per style, or one per declared channel leg where the depth is set channel by channel
- [Set colour depths](https://docs.tightly.io/help/commitments/act-set-colour-depths): Set colour depths records units per colourway for one style on one commitment, and writes the style's depth and its colour split in one transaction, so a half-written pair cannot exist: a failure anywhere leaves neither changed
- [The agreed book](https://docs.tightly.io/help/commitments/agreed-book): What has one account confirmed for this commitment, style by style, at what price, and how does that compare with last time and the money declared?
- [Buy envelope](https://docs.tightly.io/help/commitments/buy-envelope): The buy envelope is the money a commitment may place in total, at cost, held in dollars (a Bench group reads its figures in the commitment's currency at the rate served for it): the living envelope every other money figure on the commitment is read against
- [Capital](https://docs.tightly.io/help/commitments/capital): How much cash is in this book's stock, how old is it, and which way is it moving?
- [Channel scope on money](https://docs.tightly.io/help/commitments/channel-scope-on-money): On [Buy plan](../commitments/the-desk), where the styles of a commitment scoped to a channel would be worked:
- [Release the chase](https://docs.tightly.io/help/commitments/chase-release): Which style has won, how much of the reserve goes to chasing it, and what does the release leave held?
- [Chase reserve](https://docs.tightly.io/help/commitments/chase-reserve): The chase reserve is the part of the buy enve
…Machine-readable: GET /v1/resolve?q=tightly.io · GET /v1/domain/tightly.io · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage tightly.io, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for tightly.io:
1. POST https://agentwebmap.com/v1/sites/tightly.io/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://tightly.io/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/tightly.io/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/tightly.io).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.