Metadata-Version: 2.4
Name: mochi-analytics-hikari
Version: 0.2.0
Summary: hikari adapter for Mochi - auto-instruments commands, guild joins/leaves, and health snapshots
Project-URL: Homepage, https://github.com/mochi-analytics/mochi-py
Project-URL: Repository, https://github.com/mochi-analytics/mochi-py
Project-URL: Bug Tracker, https://github.com/mochi-analytics/mochi-py/issues
Author-email: Mochi Analytics <contact@bwmp.dev>
License-Expression: Apache-2.0
License-File: LICENSE
Keywords: analytics,bot,discord,hikari,mochi
Classifier: Framework :: AsyncIO
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: Apache Software License
Classifier: Programming Language :: Python :: 3
Requires-Python: >=3.10
Requires-Dist: hikari>=2.0.0
Requires-Dist: mochi-analytics>=1.0.0
Provides-Extra: dev
Requires-Dist: pytest-asyncio>=0.23; extra == 'dev'
Requires-Dist: pytest>=8; extra == 'dev'
Description-Content-Type: text/markdown

# mochi-analytics-hikari

hikari adapter for Mochi analytics.

## Install

```sh
pip install mochi-analytics mochi-analytics-hikari hikari
```

## Usage

```python
import hikari
from mochi_analytics import MochiClient
from mochi_analytics_hikari import attach_mochi

mochi = MochiClient(url="https://mochi.example.com", api_key="mochi_sk_...")

bot = hikari.GatewayBot(token="...")
detach = attach_mochi(bot, mochi)

bot.run()
```

hikari runs every shard inside one process, so one snapshot is sent per shard,
each carrying that shard's own guild count.

hikari has no built-in command framework, so `attach_mochi` records commands
straight off `InteractionCreateEvent`. For accurate `success` and `duration`,
pass `auto_track_commands=False` and wrap your handlers with `wrap_command`.

See the [hikari guide](https://docs.mochis.dev/sdks/hikari) for the full documentation.

## License

Apache-2.0
