> For the complete documentation index, see [llms.txt](https://guide.graphqleditor.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.graphqleditor.com/graphql-editor/faker-engine/instant-fake-backend.md).

# Instant Mock backend

To use and test a fake backend navigate to GraphQL Cloud via the top menu or (CTRL + K). It should automatically deploy your fake backend or warn you if something is incorrect with your schema. 

This mock backend is deployed out of the box, however it can also be configured. The following options are configurable:

* Faker JS values
* User-defined values. The mock backend will choose a random value/values - for an array from the defined values

<figure><img src="/files/2TXR1C0XqEC0k7xKVkn1" alt=""><figcaption></figcaption></figure>

### Using Faker backend in your frontend apps

To use faker backend inside frontend apps. Please make requests to&#x20;

`https://faker.graphqleditor.com/YOUR_NAMESPACE/YOUR_PROJECT/graphql`


---

# 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://guide.graphqleditor.com/graphql-editor/faker-engine/instant-fake-backend.md?ask=<question>&goal=<endgoal>
```

`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.