> For the complete documentation index, see [llms.txt](https://docs.solcis.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solcis.ai/partners/sell/register-an-opportunity.md).
# Register an opportunity
Register a client opportunity with Solcis, as an existing partner or with your first opportunity as a new one.
Register each client opportunity with us as soon as you can, so we can support you on solution design and account planning. If you are not yet a partner, registering your first opportunity starts your application.
## Opportunity exclusivity
The first partner to register an opportunity is given conditional exclusivity on it, so register early.
Before you register, check the opportunity against [Qualifying an opportunity](/partners/sell/qualifying-an-opportunity.md).
## What you'll need
* Your firm and contact details
* The client's company, contact and location
* An expected close date
Register an opportunityQualification guide
## What happens next
A member of the Solcis team will be in touch to discuss next steps. Registration terms are set in the partner agreement.
---
# 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.solcis.ai/partners/sell/register-an-opportunity.md?ask=&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.