> For the complete documentation index, see [llms.txt](https://atomico.gitbook.io/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atomico.gitbook.io/doc/api.md).

# API

- [Props(Properties)](https://atomico.gitbook.io/doc/api/props.md): The props in Atomico are the way to associate the webcomponent properties and reactive attributes that trigger the logic or interface of the webcomponent.
- [Value cycle as prop](https://atomico.gitbook.io/doc/api/props/value-cycle-as-prop.md): Atomico has a really efficient and simple type validation method, the type validation works in the following way:
- [VirtualDOM](https://atomico.gitbook.io/doc/api/virtualdom.md): Atomico's virtualDOM is designed to enhance the use of webcomponents.
- [Advanced](https://atomico.gitbook.io/doc/api/virtualdom/advanced.md)
- [Hooks](https://atomico.gitbook.io/doc/api/hooks.md): Improves the experience of reusing logic between webcomponents based on Atomico
- [useProp](https://atomico.gitbook.io/doc/api/hooks/useprop.md): Reactivity in the scope of the webcomponent without the use of context(this)
- [useEvent](https://atomico.gitbook.io/doc/api/hooks/useevent.md): Dispatch events from the webcomponent without referencing the context(this)
- [useRef](https://atomico.gitbook.io/doc/api/hooks/useref.md): Create a persistent object between renders to capture from a node from VirtualDOM
- [useHost](https://atomico.gitbook.io/doc/api/hooks/usehost.md): Hook that creates a reference that curren is the instance of the webcomponent.
- [useState](https://atomico.gitbook.io/doc/api/hooks/usestate.md)
- [useReducer](https://atomico.gitbook.io/doc/api/hooks/usereducer.md)
- [useEffect, useLayoutEffect and useInsertionEffect](https://atomico.gitbook.io/doc/api/hooks/useeffect-y-uselayouteffect.md): Allows to run side effects after rendering
- [useMemo and useCallback](https://atomico.gitbook.io/doc/api/hooks/usememo-y-usecallback.md)
- [useUpdate](https://atomico.gitbook.io/doc/api/hooks/useupdate.md): Force an update, ideal for working with references
- [useId](https://atomico.gitbook.io/doc/api/hooks/useid.md)
- [useContext](https://atomico.gitbook.io/doc/api/hooks/usecontext.md): Since version Atomico@1.62.0  has introduced a context api as part of the core.
- [useProvider](https://atomico.gitbook.io/doc/api/hooks/usecontext/useprovider.md): Allows the host that instantiates this useProvider to become the context.
- [usePromise](https://atomico.gitbook.io/doc/api/hooks/usepromise.md): Easily observe asynchronous processes
- [useAsync and useSuspense](https://atomico.gitbook.io/doc/api/hooks/useasync-and-usesuspense.md): suspend the execution of a render until the resolution of an asynchronous process
- [useAbortController](https://atomico.gitbook.io/doc/api/hooks/useabortcontroller.md): Atomico now introduces a new hook called useAbortController, which allows aborting the execution of asynchronous calls, example:
- [Testing](https://atomico.gitbook.io/doc/api/testing.md)
- [Render cycle](https://atomico.gitbook.io/doc/api/testing/test-dom.md): Atomico optimizes the execution of your script by minimizing resources through the rendering control.
- [atomico/test-hooks](https://atomico.gitbook.io/doc/api/testing/test-hooks.md): Build test to custom hooks created with Atomico with an isolated instance and predictable
- [atomico/test-dom](https://atomico.gitbook.io/doc/api/testing/atomico-test-dom.md)


---

# 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://atomico.gitbook.io/doc/api.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.