> 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/advanced-topics/providers/provider-onmissingmethod-proxy.md).

# Provider onMissingMethod Proxy

Thanks to our ColdBox Evangelist, Brad Wood, we have a feature in our Providers that you can leverage its `onMissingMethod()` to proxy calls into the provided object itself. So let's say our provided object has a method called `sayHello()`, then with an injected provider you must do this:

```javascript
property name="chatter" inject="provider:Chat";

function useChatter(){
    return chatter.get().sayHello();
}
```

That is great, but you can proxy calls into the provider itself by removing the extra `get()` call and doing this:

```javascript
property name="chatter" inject="provider:Chat";

function useChatter(){
    return chatter.sayHello();
}
```

The WireBox provider object (`wirebox.system.ioc.Provider`) has an `onMissingMethod()` function that will take all missing method calls and proxy them to the provided object. Now, this is great but be ready to lose on performance if you use this approach. That is the only caveat to this approach, is that you will be impacted by performance, not crazy, but try it.


---

# 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/advanced-topics/providers/provider-onmissingmethod-proxy.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.