> For the complete documentation index, see [llms.txt](https://altme-documentation.gitbook.io/altmes-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://altme-documentation.gitbook.io/altmes-documentation/alme-wallet/wallet-rendering.md).
# Wallet rendering
Wallet rendering is defined by this standard
In the wallet card details screen the Title of the card and Subtitle of the card are attributes “title” an “subtitle” from the output\_descriptors.display. The accordion “Description” is the description attribute of the same output\_descriptors.diplay.
The “Informations” accordion of Altme is made up of all properties of the output\_descriptors.properties.
Altme supports type “string” with specific format “email”, “uri”, “date”, hour” and other types as “number”, “integer” and “bool”. See an example here :
```
{ "output_descriptors":[
{
"id": "00000000",
"schema": "Test",
"display": {
"title": {
"path": [],
"schema": {
"type": "string"
},
"fallback": "VC for Test"
},
"subtitle": {
"path": [],
"schema": {
"type": "string"
},
"fallback": "Type and format"
},
"description": {
"path": [],
"schema": {
"type": "string"
},
"fallback": "This VC is made up for testing prupose."
},
"properties": [
{
"path": ["$.credentialSubject.integer"],
"schema": {
"type": "integer"
},
"fallback": "Unknown",
"label": "integer"
},
{
"path": ["$.credentialSubject.number"],
"schema": {
"type": "number"
},
"fallback": "Unknown",
"label": "number"
},
{
"path": ["$.credentialSubject.bool"],
"schema": {
"type": "bool"
},
"fallback": "Unknown",
"label": "bool"
},
{
"path": ["$.credentialSubject.uri"],
"schema": {
"type": "text",
"format" : "uri"
},
"fallback": "Unknown",
"label": "uri"
},
{
"path": ["$.credentialSubject.email"],
"schema": {
"type": "text",
"format" : "email"
},
"fallback": "Unknown",
"label": "email"
}
]
}
```
!\[Example of a card details screen ]\()
An example here with output descriptors :
```
{
"id":"PC_01",
"issuer":{
"id":"did:tz:tz1NyjrTUNxDpPaqNZ84ipGELAcTWYg6s5Du",
"name":"Talao issuer",
"styles": {
"thumbnail": {
"uri": "https://talao.mypinata.cloud/ipfs/QmU8z1aDDpbgVjXwU8nMvgU3YD4VeUzHTkitsELZRFBBZa",
"alt": "Talao logo"
},
"background": {
"color": "#ffffff"
},
"text": {
"color": "#d4d400"
}
}
},
"output_descriptors":[
{
"id": "PCDS_01",
"schema": "PCDSAuditorCertificate",
"display": {
"title": {
"path": ["$.name"],
"schema": {
"type": "string"
},
"fallback": "Title fallback"
},
"subtitle": {
"path": ["$.description"],
"schema": {
"type": "string"
},
"fallback": "Subtitle fallback"
},
"description": {
"text": "This is an electronic version of a PCDS auditor certificate for testing purposes."
},
"properties": [
{
"path": ["$.credentialSubject.category"],
"schema": {
"type": "string"
},
"fallback": "Unknown category",
"label": "Certificate category"
},
{
"path": ["$.credentialSubject.familyName"],
"schema": {
"type": "string"
},
"fallback": "Unknown auditor name",
"label": "Auditor name"
},
{
"path": ["$.credentialSubject.certificationDate"],
"schema": {
"type": "string"
},
"fallback": "Unknown certification date",
"label": "Certification Date"
},
{
"path": ["$.credentialSubject.validity"],
"schema": {
"type": "string"
},
"fallback": "Unknown validity",
"label": "Certificate validity"
}
]
}
}
],
"presentation_definition":{}
}
```
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://altme-documentation.gitbook.io/altmes-documentation/alme-wallet/wallet-rendering.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.