# Caching

Caching requests executed by Actions is a common practice. NGXS does not provide this ability out of the box, but it is easy to implement.

There are many different ways to approach this. Below is a simple example of using the store's current values and returning them instead of calling the HTTP service.

```typescript
import { State, Action, StateContext } from '@ngxs/store';
import { of } from 'rxjs/observable/of';
import { tap } from 'rxjs/operators';

export class GetZebra {
  static readonly type = '[Zoo] GetZebra';
  constructor(public id: string) {}
}

@State<ZooStateModel>({
  defaults: {
    zebras: []
  }
})
export class ZooState {

  constructor(private animalService: AnimalService) {}

  @Action(GetZebra)
  getZebra(ctx: StateContext<ZooStateModel>, action: GetZebra) {
    const state = ctx.getState();
    // payload = id of animal
    const idx = state.zebras.findIndex(zebra => zebra.id === action.id);
    if (idx > -1) {
      // if we have the cache, just return it from the store
      return dispatch(new GetZebraSuccess(state.zebras[idx]));
    } else {
      return this.animalService.getZebra(action.id).pipe(
        map(resp => dispatch(new GetZebraSuccess(resp)))
      );
    }
  }

}
```


---

# 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://www.ngxs.io/v3.4/recipes/cache.md?ask=<question>
```

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.