Feat: enso api prices

[TxCorpi0x]

Description

Please include a summary of the changes and the related issue.

Adds integration to Enso API prices endpoint to retrieve the token price by chain ID and contract address of token

Type of Change

• Bugfix
• New Feature
• Improvement
• Documentation Update

Checklist

• I have read the contributing guidelines.
• I have added tests to cover my changes.
• All new and existing tests passed.

Related Issue

Closes #[issue number]

[hyacinthus]

How can AI know the chain ID?

Additionally, please forgive my lack of understanding regarding enso. Does it have to be cross-chain, or is cross-chain optional? Have you talked to Eric about the chain? Is it possible to limit the functionality to a single chain? For example, if a user sets the base, can it only operate on that base?

We can enhance its stability by reducing the scope of skills. If cross-chain is necessary, we can also provide it with a whitelist.

[TxCorpi0x]

How can AI know the chain ID?

Additionally, please forgive my lack of understanding regarding enso. Does it have to be cross-chain, or is cross-chain optional? Have you talked to Eric about the chain? Is it possible to limit the functionality to a single chain? For example, if a user sets the base, can it only operate on that base?

We can enhance its stability by reducing the scope of skills. If cross-chain is necessary, we can also provide it with a whitelist.

The chain id is optional and its default value is 1 which is Ethereum mainnet, I have not seen the rest of the chains in their results so far, and the concentration is on Ethereum mainnet.
Enso Wallet Approval smart router contract is on Ethereum and so far it has been all around mainnet. I put the chainId as 1 by default to prevent confusion of AI side. but if the user asks a particular chain id, it will be handled by the tool and will set int he API call input.
Whitelisting the Chain IDs is a great option which can be added as an enhancement in the future.