> For the complete documentation index, see [llms.txt](https://docs.pyck.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pyck.cloud/graphql-api/scalars/float.md).

# Float

Double-precision floating-point scalar type

Audience: Programmer

The `Float` scalar type represents signed double-precision fractional values as specified by IEEE 754.

## Format

* 64-bit IEEE 754 floating-point
* Approximately 15-17 decimal digits of precision
* Range: ±1.7976931348623157E+308
* Supports scientific notation

## Usage

```graphql
type ItemMovement {
  quantity: Float!
  unitPrice: Float
  totalValue: Float
}

mutation {
  createItemMovement(input: {
    quantity: 10.5
    unitPrice: 29.99
  }) {
    itemMovement {
      totalValue  # Returns Float
    }
  }
}
```

## Common Float Fields

* Quantities with decimals
* Prices and monetary values
* Percentages and ratios
* Coordinates (latitude/longitude)
* Measurements and dimensions

## Precision Considerations

```graphql
# Be aware of floating-point precision
mutation {
  updatePrice(
    value: 0.1 + 0.2  # May not equal exactly 0.3
  )
}
```

## Best Practices

1. Use for scientific calculations
2. Consider fixed-point for money (or use Int for cents)
3. Be aware of precision limitations
4. Use rounding when displaying to users

## See Also

* [Int](/graphql-api/scalars/int.md) - Whole number values
* [String](/graphql-api/scalars/string.md) - For arbitrary precision decimals


---

# 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://docs.pyck.cloud/graphql-api/scalars/float.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.