> For the complete documentation index, see [llms.txt](https://wirebox.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wirebox.ortusbooks.com/5/advanced-topics/providers/virtual-provider-lookup-methods.md).

# Virtual Provider Lookup Methods

This is a feature where you can mark methods in your components with a special `provider` annotation so they can serve the objects you requested automatically for you. This is an amazing feature as it will take the original method signature and replace the method for you with one that will serve the provided objects for you automatically. How insane is that! You deserve some **getting jiggy wit it (chapter 4)** dancing!

```javascript
public Espresso function getEspresso() provider="espresso"{}
```

Wow! That's it! Yep, just create an empty method signature and annotated with `provider={mapping}` and then WireBox will read these annotated methods and replace them for you at runtime so when you call `etEspresso()` it actually calls the WireBox injector and requests a new espresso instance and it returns it.

> **Caution** Please note that the visibility of provided methods does not matter to WireBox. It can provide `public, private, or packaged` visibilities with no problem at all.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wirebox.ortusbooks.com/5/advanced-topics/providers/virtual-provider-lookup-methods.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.