# API Recipes

Open API and SDK<br>

Our ultimate goal is to provide an essential open API and SDK from a high-level perspective with the above tools, fully powering NFT use cases in private economies on Polkadot. The functionality can be utilized via Open API and SDK. This will be released to combine all components.&#x20;

The benefits of an open API are beyond criticism. We hope to build a framework whereby a plethora of diverse features can find expression, value, and explosive operationalization in the Polkadot ecosystem.&#x20;

The SDK will be both an extension of the builders’ capabilities and an extension of the value proposition of the Polkadot universe as a whole. If successful, this sort of solution brings more reliability and robustness to theentire network, as OCWs will be more than the external reference, they will become the enablers of a validated on-chain repository of trusted information for the entire Polkadot network.

!\[Shape

Description automatically generated with low confidence]\(<https://lh5.googleusercontent.com/I9fMrfrEN7ViLSr4CZEbXOVGpeZawoUgWRG6bwKn3FJcGblUwQ5n9yJBB9yJVN7yHbScHnLJYN4daqsTm3okwCF56BvGlUtS4mx_RNrQ9osM5AJtLEq5pnXBvdHH6OgDnyihhrusDqteNZZ3Kqkh76gFNA>)

\
Hasura - Unified API Engine

<br>

<figure><img src="https://lh4.googleusercontent.com/EctWmKrfe5JQrL1VGJ1jVzg7sDyOw2FoLt-ycwVAtuWOk6CWP0x0GaaYlNDEM0lm2pntLlIDtN1c-p2Rwy94jdKzvyJgt0rPkSQIomdVjg9qCM6vifSuFlBLJurzEGVQ_Z_b7JVjZUqA7nY-D_0j8tWpdQ" alt=""><figcaption></figcaption></figure>

## API Features

* Blazing fast API performance, accessible data modelling
* Aggregates API for all micro-services and enterprise components
* Intuitive REST and GraphQL interface for internal and external developers
* Horizontal scalability<br>

API Features<br>

Create and Manage Assets

Issue your unique assets in the form of unique (non-fungible) tokens on the blockchain - in minutes with a simple API interface. SugarFunge API uses the widely adopted Substrate Smart Contracts and ERC721 token standard through Ethereum bridge which can be used for a broad range of use cases and applications.

\ <br>

Decentralized at its core

The SugarFunge API is the first fully decentralized web service built on top of the existing SugarFunge open-source infrastructure, which wraps SugarCubes functionalities in a common API interface. The goal was to build a familiar API service without compromising the core value of blockchain and decentralization.

<br>

Atomic Operations

Many-to-many atomic operations are the cornerstone of the SugarFunge API. An atomic operation is a set of instructions for what you will execute in a single transaction and with only two possible results. Either the transaction will succeed, and all participants will receive their assets, or the transaction will fail, and the operation will return to its starting point.

<br>

Set User Abilities

Assign different access and management rights to users or team members and add flexibility to the creation and control of your blockchain-based assets.

\ <br>

Cut Down on Development Cost

The SugarFunge API was built for fast adoption. Instead of dedicating large resources, extended periods of development time and extensive security audits, you can start building on day one. The entire SugarFunge infrastructure was audited and allows you to deploy decentralized applications within minutes.

<br>


---

# Agent Instructions: 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:

```
GET https://envida-protocol.gitbook.io/envida/api-recipes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.