> For the complete documentation index, see [llms.txt](https://www.ftcwiki.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.ftcwiki.org/manufacturing-and-assembly/materials/stainless-steel-alloys.md).

# Stainless Steel Alloys

{% tabs %}
{% tab title="304-2B" %}
304 stainless steel is a strong, corrosion-resistant material commonly used in projects where long-term durability is essential. It is one of the most versatile stainless steels available, offering excellent weldability, good formability, and resistance to rust and oxidation.

For FTC teams, laser-cut 304 stainless steel can be a reliable option for components exposed to moisture, wear, or outdoor conditions. Its corrosion resistance makes it especially useful for parts that must maintain strength and appearance over time, such as structural supports or hardware on demo robots used outside the competition environment.

While it is heavier and more difficult to machine than aluminum or mild steel, 304 stainless is unmatched in durability and cleanliness. It's widely used in industries like food service, marine construction, and architecture for the same reasons.

For applications requiring even higher corrosion resistance—such as exposure to saltwater or chemicals—316 stainless steel may be a better alternative, offering enhanced protection in the harshest environments.
{% endtab %}
{% endtabs %}


---

# 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://www.ftcwiki.org/manufacturing-and-assembly/materials/stainless-steel-alloys.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.
