> For the complete documentation index, see [llms.txt](https://checkin.gitbook.io/checkin-litepaper-v0.1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://checkin.gitbook.io/checkin-litepaper-v0.1/gameplay.md).

# Gameplay

There are two basic ways to engage with Checkin - through Warpcast or through the Checkin PWA client app.  Primary mechanic or core mechanic of Checkin is to checkin when visiting different locations to signal your arrival/visit.  By checking in, you create an entry on your profile of your visit and you get rewarded corresponding number of points depending on a variety of factors. 

### Checking In on Warpcast:

1. Tag @checkin in a new cast in Warpcast
2. Copy/paste GoogleMaps link for the location
3. Cast to the /checkin channel and earn points

{% embed url="<https://www.youtube.com/watch?v=8xDyIv7Sjus>" %}

### Checking In on Checkin Caster client:

Note:

* If you check in with our client app, you will get 5x points compared to from Warpcast client!

1. Install Checkin Caster client at <https://app.checkincaster.xyz>
2. Click on location pin and select location from dropdown
3. Cast to the /checkin channel and earn Points

{% embed url="<https://www.youtube.com/watch?v=rTT_LjXHIDc>" %}

{% hint style="info" %}
When signing up, you may encounter a popup asking you to pay in warps - this is because Warpcast stops sponsoring after a user has 3 keys sponsored by the same account (e.g. Privy). After that, they will be prompted to pay with Warps.
{% 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 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://checkin.gitbook.io/checkin-litepaper-v0.1/gameplay.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.