Details Grade Damage Code Lookup
Bounded offline reference: Details grades describe qualifying impairment while separately describing remaining wear-level detail. Source: PCGS/NGC grading descriptions. Damage-code vocabulary differs by service/edition; details is not a universal numeric deduction or authenticity guarantee. Supported topic keys: summary, reference, limitations. No complete external corpus or live policy implied.
Description
A details-grade code describes a condition issue under a particular service convention.
A details-grade code describes a condition issue under a particular service convention.1
This lookup explains the chosen topic using a bounded stored reference.
When to use Details Grade Damage Code Lookup
Use this tool to read a bounded explanation for an exact reference topic. Establish the coin issue, source edition, measurement basis and reference date where applicable.
How to use Details Grade Damage Code Lookup and understand its results
- Establish the coin issue, source edition, measurement basis and reference date where applicable.
- Enter topic, using the field meanings and rules below, then run the tool.
- Read result. Inspect nested result fields where present, and review unknown records separately from known matches.
- Correct any reported input issue and run again. Before using a successful result, check the stated units, signs, reference scope and observation coverage.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| topic | Topic | string | Required |
Choose one exact topic token from the table. The implementation looks up the stored value and returns it in the documented output field. Matching is case-sensitive; unrecognized tokens fail. This is an offline bounded reference, not a live catalogue or independent attribution.
| Topic token | Stored value |
|---|---|
| summary | Details grades describe qualifying impairment while separately describing remaining wear-level detail. |
| reference | PCGS/NGC grading descriptions. |
| limitations | Damage-code vocabulary differs by service/edition; details is not a universal numeric deduction or authenticity guarantee. |
value=referenceTable[exactToken] Use the matching field units and the exact boundary, ordering and reference rules above.
| Output field | Meaning | Value type |
|---|---|---|
| result | Calculated observation or qualified reference | object |
| result.text | text | string |
{
"input": {
"topic": "summary"
},
"output": {
"result": {
"text": "Details grades describe qualifying impairment while separately describing remaining wear-level detail."
}
}
}Limitations and assumptions
Coin identification, reference applicability and measurement uncertainty require separate evidence. A returned explanation or arithmetic agreement does not establish authenticity, a certified grade or a current market value. Damage-code vocabulary differs by service/edition; details is not a universal numeric deduction or authenticity guarantee.
Missing required fields, unknown fields, wrong types and violated rules return input issues. Numeric values and outputs must be finite. Extremely large composite outputs are rejected.
Alternative or Complementary methods
For a related step, use Bodybag No Grade Common Rejection Reasons List: A no-grade submission result depends on the service’s documented rejection category. For a complementary comparison, use Grade Description Lookup: Adjectival grade descriptions summarize visible condition at a broad collecting level.
References
-
Details Grade Damage Code Lookup — tool.io
Similar or alternative tools
- Bodybag No Grade Common Rejection Reasons List
A no-grade submission result depends on the service’s documented rejection category.
- Grade Description Lookup
Adjectival grade descriptions summarize visible condition at a broad collecting level.