> For the complete documentation index, see [llms.txt](https://docs.useprecursor.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.useprecursor.xyz/resources/brand.md).

# Brand and channels

What the Precursor name means, how to write it, how Precursor sounds, and the official channels it speaks from.

## The name

A precursor is the thing that comes before. Private markets are where public companies come from, and Precursor is built for that stage: the years when a company is growing, raising and rewarding the people who built it, before it ever lists.

## Writing the name

* **Precursor** is one word with a single capital P. It isn't set in all capitals in running text, and it isn't abbreviated.
* Product names take the name in front: **Precursor Console**, **Precursor Portfolio**, **Precursor Explorer**, **Precursor API**. After the first mention on a page, "Console", "Portfolio" and "Explorer" are fine on their own.
* Tokens are **Precursor Share Tokens**, or "share tokens" after the first mention. Avoid "coins" and "crypto stocks".
* Precursor's relationship to the network is always written as **built on Robinhood Chain**. Precursor is an independent company. Never describe it as a partner of, endorsed by or affiliated with Robinhood, or with any company that hasn't onboarded.

## Voice

Precursor writes like infrastructure: precise, calm and technical, and credible enough for a CFO to forward to the board.

1. **Precise over promotional.** Say "holding periods enforced at the contract level", not "fully secure". Name the contract, the event or the rule.
2. **Show the mechanism.** Use interfaces, tables, transaction hashes and Explorer links instead of adjectives.
3. **Respect the reader.** Explain what an action does before someone takes it, in plain language, and say what can't be undone.
4. **No crypto vernacular.** No "moon", "degen", "airdrop" or memecoin imagery. Use "stock tokens", "share classes", "settlement" and "holders".
5. **Plain sentences.** Short paragraphs, active voice, one idea at a time. No exclamation marks.

### Words we use and words we avoid

| Use                        | Avoid                        |
| -------------------------- | ---------------------------- |
| Share token, stock token   | Coin, crypto stock           |
| Holder, shareholder        | Degen, whale, bag holder     |
| Liquidity Window           | Unlock event, pump           |
| Settlement, clearing price | Moon, price action           |
| Issuer-sponsored           | Official, partnered          |
| Eligible investors         | Everyone, anyone, the masses |

## Sample copy

* **Headline:** Equity infrastructure for the companies that come next.
* **Subhead:** Precursor lets private companies issue stock tokens on Robinhood Chain, with every issuance, transfer and corporate action settled transparently on-chain.
* **Calls to action:** Start tokenizing · Read the documentation · View on Explorer
* **Trust line:** Issuer-sponsored · ERC-3643 · Settled on Ethereum via Robinhood Chain · Audited
* **One line:** Precursor is to private-company equity what payments infrastructure is to commerce: the programmable layer that turns a slow, manual process into an API.

## Official channels

| Channel           | Address                                                                  |
| ----------------- | ------------------------------------------------------------------------ |
| Website           | [useprecursor.xyz](https://useprecursor.xyz)                             |
| Documentation     | [docs.useprecursor.xyz](https://docs.useprecursor.xyz)                   |
| Console           | [app.useprecursor.xyz/console](https://app.useprecursor.xyz/console)     |
| Portfolio         | [app.useprecursor.xyz/portfolio](https://app.useprecursor.xyz/portfolio) |
| Explorer          | [explorer.useprecursor.xyz](https://explorer.useprecursor.xyz)           |
| API               | `https://api.useprecursor.xyz/v1`                                        |
| X                 | [@useprecursor](https://x.com/useprecursor)                              |
| GitHub            | [github.com/useprecursor](https://github.com/useprecursor)               |
| General enquiries | <hello@useprecursor.xyz>                                                 |
| Support           | <support@useprecursor.xyz>                                               |
| Security reports  | <security@useprecursor.xyz>                                              |

{% hint style="warning" %}
Precursor will never ask for a seed phrase or private key, and never asks you to send funds to an address by email or direct message. Contract addresses are published only in the Explorer and through `GET /v1/contracts`. Treat any other domain, handle or address as not Precursor.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.useprecursor.xyz/resources/brand.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
