> For the complete documentation index, see [llms.txt](https://wiki.greatcollaboration.uk/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.greatcollaboration.uk/knowledgebase/mitigation/capturingco2.md).

# CapturingCO2

Direct Air Capture using COF-992

Researchers at the University of California, Berkeley, USA, have developed a new porous material that efficiently captures CO₂ from ambient air without degradation.

DAC (Direct Air Capture) The porous material COF-999 — a covalent organic framework (COF) — captures CO2 from ambient air without degradation by water or other contaminants, one of the limitations of existing DAC technologies.

The new material could be substituted easily into carbon capture systems already deployed or being piloted to remove CO2 from refinery emissions and capture atmospheric CO2 for storage underground.

UC Berkeley graduate student Zihui Zhou, the paper’s first author, said that a mere 200 grams of the material, a bit less than half a pound, can take up as much CO2 in a year — 20 kilograms (44 pounds) — as a tree.

{% embed url="<https://superinnovators.com/2024/10/capturing-carbon-from-the-air-just-got-easier/?utm_campaign=superinnovators-weekly-newsletter-1-2&utm_medium=email&utm_source=mailpoet&utm_source_platform=mailpoet>" %}


---

# 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://wiki.greatcollaboration.uk/knowledgebase/mitigation/capturingco2.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.
