> For the complete documentation index, see [llms.txt](https://docs.coti.io/coti-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coti.io/coti-documentation/private-messaging/skills/skill-2.md).

# COTI Starter Grant

Handles one-time gas funding for a newly created wallet.

## Overview

New wallets cannot interact with COTI until they have some native COTI for gas. This workflow wraps the challenge-response flow used to fund an eligible wallet for the first time.

## Prerequisites

* the private messaging MCP server must be connected
* a wallet must already be configured
* the starter grant service must be available to the MCP server

## Typical workflow

### Recommended flow

1. Call `request_starter_grant`.
2. Check that the result status is `claimed`.
3. Confirm the wallet balance through a transaction or balance tool.

### Manual flow

1. Call `get_starter_grant_status`.
2. If eligible, call `get_starter_grant_challenge`.
3. Answer the lightweight challenge.
4. Call `claim_starter_grant`.

## Tool reference

### `request_starter_grant`

Runs the full challenge and claim sequence in one call.

### `get_starter_grant_status`

Returns one of:

* `eligible`
* `challenge_pending`
* `claimed`

### `get_starter_grant_challenge`

Returns the challenge prompt, challenge ID, claim payload, and expiry.

### `claim_starter_grant`

Signs the claim payload with the configured wallet and submits the claim.

## Common failures

* the wallet already claimed its one-time grant
* the challenge expired
* the starter grant service is unreachable
* the local install ID state is inconsistent

## Important notes

* the grant is one-time per wallet
* the challenge is intentionally simple
* the install ID is a soft deduplication signal, not a trustless identity primitive
* after claiming, the wallet should have enough COTI for initial messaging activity


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coti.io/coti-documentation/private-messaging/skills/skill-2.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.