> For the complete documentation index, see [llms.txt](https://docs.slinky.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.slinky.network/understanding-slinkylayer/how-slinkylayer-works.md). # How SlinkyLayer works SlinkyLayer sits at the intersection of APIs, payments, and machine-native access. If you are a provider, you can take something valuable you already run, such as a model endpoint, an API, a data service, or a tool, and expose it as a metered resource. If you are a consumer, you do not need to enter a long commercial relationship just to use it. You make a request, pay for that request, and receive the result. If you are building agents, this becomes even more important. Agents need the ability to use external tools on demand. They need to fetch data, call models, enrich context, and perform actions during execution. Traditional API infrastructure puts a bureaucratic wall in front of that behavior. SlinkyLayer removes much of that wall. The result is a simpler exchange: * A provider offers a resource * A consumer discovers it * The consumer pays per call * Access is granted immediately * The provider is paid immediately That flow sounds obvious once you say it out loud. The strange part is that the web has spent years making it harder than necessary. --- # 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.slinky.network/understanding-slinkylayer/how-slinkylayer-works.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.