# READY

On a READY event, the callback will fire with a single argument with information about the wallet provider. At any time a READY event listener is added, it will immidiately be called if the provider is already in a ready state. This provides a single flow for dapp developers since this listener should start any and all interactions with the dapi protocol.

<table><thead><tr><th width="327">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><code>name: string</code></td><td>The name of the wallet provider</td></tr><tr><td><code>website: string</code></td><td>The website of the wallet provider</td></tr><tr><td><code>version: string</code></td><td>The version of the dAPI that the the wallet supports</td></tr><tr><td><code>compatibility: string[]</code></td><td>A list of all applicable NEPs which the wallet provider supports</td></tr><tr><td><code>extra: object</code></td><td>Provider specific attributes</td></tr></tbody></table>

## Example

```js
window.addEventListener('NEOLine.NEO.EVENT.READY', () => {
    console.log('dAPI common method loading is complete.');
});
```


---

# Agent Instructions: 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:

```
GET https://tutorial.neoline.io/reference/neo3-provider-api-legacy/common-events/ready.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.