···

       
41
       
 
       


     

       
42
       
 
       
Two core standard query APIs are supported to balance convenience and trust. They both fetch [records](https://atproto.com/guides/glossary#record):

     

       
43
       
 
       


     

       
44
       
-
       
### [`com.atproto.repo.getRecord`](#tag/comatproto-queries/GET/xrpc/com.atproto.repo.getRecord)

     

       
45
       
 
       


     

       
46
       
 
       
- convenient `JSON` response format

     

       
47
       
 
       
- cannot be proven authentic

     

       
48
       
 
       


     

       
49
       
-
       
### [`com.atproto.sync.getRecord`](#tag/comatproto-queries/GET/xrpc/com.atproto.sync.getRecord)

     

       
50
       
 
       


     

       
51
       
 
       
- [`DAG-CBOR`](https://atproto.com/specs/data-model)-encoded response requires extra libraries to decode, but

     

       
52
       
 
       
- includes a cryptographic proof of authenticity!

     
···

       
58
       
 
       


     

       
59
       
 
       
- Slingshot also offers variants of the `getRecord` endpoints that accept a full `at-uri` as a parameter, to save clients from needing to parse and validate all parts of a record location.

     

       
60
       
 
       


     

       
61
       
-
       
- Bi-directionally verifying identity endpoints, so you can directly exchange atproto [`handle`](https://atproto.com/guides/glossary#handle)s for [`DID`](https://atproto.com/guides/glossary#did-decentralized-id)s without extra steps, plus a convenient [Mini-Doc](#tag/slingshot-specific-queries/GET/xrpc/com.bad-example.identity.resolveMiniDoc) verified identity summary.

     

       
62
       
 
       


     

       
63
       
 
       


     

       
64
       
 
       
## Part of microcosm

     

···

       
41
       
 
       


     

       
42
       
 
       
Two core standard query APIs are supported to balance convenience and trust. They both fetch [records](https://atproto.com/guides/glossary#record):

     

       
43
       
 
       


     

       
44
       
+
       
### [`com.atproto.repo.getRecord`](#tag/comatproto-queries/get/xrpc/com.atproto.repo.getRecord)

     

       
45
       
 
       


     

       
46
       
 
       
- convenient `JSON` response format

     

       
47
       
 
       
- cannot be proven authentic

     

       
48
       
 
       


     

       
49
       
+
       
### [`com.atproto.sync.getRecord`](#tag/comatproto-queries/get/xrpc/com.atproto.sync.getRecord)

     

       
50
       
 
       


     

       
51
       
 
       
- [`DAG-CBOR`](https://atproto.com/specs/data-model)-encoded response requires extra libraries to decode, but

     

       
52
       
 
       
- includes a cryptographic proof of authenticity!

     
···

       
58
       
 
       


     

       
59
       
 
       
- Slingshot also offers variants of the `getRecord` endpoints that accept a full `at-uri` as a parameter, to save clients from needing to parse and validate all parts of a record location.

     

       
60
       
 
       


     

       
61
       
+
       
- Bi-directionally verifying identity endpoints, so you can directly exchange atproto [`handle`](https://atproto.com/guides/glossary#handle)s for [`DID`](https://atproto.com/guides/glossary#did-decentralized-id)s without extra steps, plus a convenient [Mini-Doc](#tag/slingshot-specific-queries/get/xrpc/com.bad-example.identity.resolveMiniDoc) verified identity summary.

     

       
62
       
 
       


     

       
63
       
 
       


     

       
64
       
 
       
## Part of microcosm