# Introduction to SlinkyLayer Most internet infrastructure still assumes a human is sitting at the other end. A person signs up for an account. A person enters a credit card. A person copies an API key into a dashboard, adds a billing address, chooses a plan, waits for approval, and agrees to whatever pricing model a platform has decided to impose. That system works well enough for SaaS. It works badly for software. It works especially badly for agents. An agent does not want a dashboard. It does not want a seat license. It does not want to talk to sales, request higher rate limits, or juggle a spreadsheet full of API credentials. It wants to find a resource, understand the price, pay for exactly what it needs, and move on. That is the problem SlinkyLayer is built to solve. SlinkyLayer turns any AI model or API into a pay-per-call, on-chain resource using the x402 protocol. In plain terms, it gives developers and providers a way to expose useful digital services so they can be accessed instantly and paid for one call at a time. No monthly subscription gymnastics. No awkward account provisioning. No default assumption that every interaction has to begin with human onboarding. Instead, SlinkyLayer treats compute the way the internet should have treated it all along: as something software can access directly, price clearly, and pay for in real time. --- # 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://docs.slinky.network/understanding-slinkylayer/introduction-to-slinkylayer.md?ask= ``` 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.