> For the complete documentation index, see [llms.txt](https://docs.energyweb.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.energyweb.org/legacy-documentation/solutions-2023/open-charging-network/use-the-ocn-service-interface/offer-an-ocn-service.md). # Offer an OCN Service An OCN Service Provider develops and provides OCN services that can be used by CPOs, eMSPs and other parties to improve their charging services - such as contracting, billing, payment systems etc. **The OCN Service is - similar to any other OCPI role - an OCN Party.** We make this distinction from other "Services" that might only require customers to send OCPI messages (including custom OCPI modules) directly. ### Offer your OCN Service To offer your OCN Service via the OCN Service Interface, make sure the following prerequisites are met: 1. [The OCN Service has a OCN Identity](/legacy-documentation/solutions-2023/open-charging-network/create-and-manage-an-ocn-identity.md) 2. [The OCN Service is connected to the OCN](/legacy-documentation/solutions-2023/open-charging-network/connect-an-ocpi-ocn-party-to-a-node.md) **Now you are ready to publish your OCN Service on the OCN Registry.** ### **Set Service Permissions** An OCN Service is an OCPI party that requires additional permissions from their customers. Such permissions could include the forwarding of session or charge detail record data, for example in a payment service. Once a customer/user has agreed to the Service's permissions, the OCN Node tied to the customer will automate any such required permissions, lessening the cost of integration with a service. **To be granted the aforementioned permissions, you must then list your OCN Service and the permissions required in a separate smart contract, entitled "Permissions"**. Thereafter, a user can make their agreement explicit in the same smart contract. Learn more on how to list your OCN Service on our [OCN Registry Repository](https://github.com/energywebfoundation/ocn-registry). You can find a full list of currently implemented OCN Permissions [here](https://github.com/energywebfoundation/ocn-registry/tree/develop). {% hint style="info" %} Access the full OCN technical documentation [here](https://shareandcharge.com/wp-content/uploads/2020/11/OCN-Documentation-v1.1.pdf). {% 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://docs.energyweb.org/legacy-documentation/solutions-2023/open-charging-network/use-the-ocn-service-interface/offer-an-ocn-service.md?ask=&goal= ``` `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.