> For the complete documentation index, see [llms.txt](https://docs.arkeo.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arkeo.network/arkeo-for-data-providers/management.md).

# Ongoing Management

This document outlines management tasks for maintaining your Arkeo provider services, including querying your provider details and understanding the service enum mappings used in Arkeo.

## Querying Provider Details

To view detailed information about your registered provider, filter by your provider public key (pub\_key) using the following command:

```
arkeod query arkeo list-providers --output json | jq '.provider[] | select(.pub_key=="<your-provider-pubkey>")'
```

## Listing Active Contracts by Provider

To list all active contracts associated with your provider public key (contracts where settlement height is 0), use the following command:

```
arkeod query arkeo list-contracts --output json | jq '.contract[] | select(.provider=="<your-provider-pubkey>" and .settlement_height=="0")'
```

## Best Practices

* Regularly query your provider details to ensure your service information is current and accurate.
* Periodically check your active contracts to manage settlements effectively.
* Understand the service mapping clearly when adding or updating your provider offerings.
* Regular monitoring and periodic verification ensure maximum reliability and client satisfaction.

## Arkeo Supported Services

Use either of these services for a comprehensive reference mapping between service names and their numeric identifiers, as used within Arkeo.

```
arkeod query arkeo all-services
```

```
http://localhost:1317/arkeo/services
```


---

# 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.arkeo.network/arkeo-for-data-providers/management.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.
