# Why Protocolink?

### **Simplicity and Efficiency**&#x20;

* Protocolink integrates with [**Permit2**](/use-cases/permit2-amplifier.md), saving users who have existing allowances fees from having to send token approval transactions again.
* Protocolink aggregates transactions, enabling users to send batched transactions to save gas.
* Protocolink provides an [**API**](/protocolink-api/overview.md) and an [**SDK**](/protocolink-sdk/overview.md) which:
  * Empowers developers to leverage the full composability of blockchain protocols without writing smart contracts.
  * Enables teams to deliver the minimum viable product with limited resource bandwidth.

### Security and Extensibility

* Protocolink smart contracts are non-upgradable, protecting users from unforeseen upgrades or changes to the contract.
* Protocolink is extensible, facilitating pull requests created by TypeScript contributors. This allows Protocolink to provide custom features for any project.
* Protocolink mitigates the risks of integrating any new protocols. New integrations have no effects on existing features and therefore require no additional contract audits!

### Endless **Possibilities**

* Protocolink includes no whitelist mechanism, empowering users and developers to aggregate any transactions to enjoy the real decentralized experience.
* Protocolink supports not only ERC20 but ERC721 and ERC1155 which are widely adopted by DeFi and NFT projects.
* Protocolink provides the latest blockchain experiences. New integrations are coming thanks to our contributors.


---

# 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://docs.protocolink.com/why-protocolink.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.
