docs: cli and sdk reference

Author: MarcosNicolau

docs/3_guides/1.3_SDK_api_reference_aggregation.md

@@ -0,0 +1,36 @@
+# Aligned SDK
+
+## API Reference for aggregation mode
+
+### `is_proof_verified_in_aggregation_mode`
+
+Checks if the proof has been verified with Aligned and is included in the batch on-chain.
+
+```rust
+pub async fn is_proof_verified_in_aggregation_mode(
+    proof_data: ProofData,
+    network: Network,
+    eth_rpc_url: &str
+    beacon_client_url: &str,
+    from_block: Option<u64>
+) -> Result<[u8; 32], ProofVerificationAggModeError>
+```
+
+#### Arguments
+
+-   `proof_data` - The proof data needed based on the provided proving system.
+-   `network` - The network on which the verification will be done (`devnet | holesky | mainnet`)
+-   `eth_rpc_url` - The URL of the Ethereum RPC node.
+
+#### Returns
+
+-   `Result<[u8; 32], ProofVerificationAggModeError>` - The merkle root of the aggregated proof.
+
+#### Errors
+
+-   `ProvingSystemNotSupportedInAggMode` if the proving system is not supported (Currently, only SP1 compressed proofs are supported).
+-   `EthereumProviderError` if there is an error in the Ethereum call.
+-   `BeaconClient` if there is an error in the Beacon client call.
+-   `UnmatchedBlobAndEventMerkleRoot` if the proof was in included in the blob but the merkle root did not match with the one in the contract
+-   `ProofNotFoundInLogs` if the proof was not found in any of the aggregated proofs from the specified block_number
+-   `EventDecoding`: if it failed to decode an event from the ProofAggregationService

docs/3_guides/9_aligned_cli.md

@@ -346,3 +346,46 @@ aligned get-user-amount-of-queued-proofs  \
 --network holesky \
 --batcher_url wss://batcher.alignedlayer.com
 ```
+
+
+---
+
+### **verify-agg-proof**
+
+#### Description:
+
+Verifies if your proof has been verified by the `ProofAggregationService`.
+
+#### Command:
+
+`cargo run verify-agg-proof [OPTIONS] --proving_system <proving_system>`
+
+#### Options:
+
+- `--vk`: Verification key hash file path.
+- `--public_input`: Your program committed values file path.
+- `--from-block`: From which block to start fetching events. This must no be older than 18 days as blobs will be expired. Defaults to the block corresponding to last 24 hours.
+- `--network <working_network_name>`: Network name to interact with.  
+  - Default: `devnet`  
+  - Possible values: `devnet`, `holesky`, `mainnet`
+- `--rpc_url <RPC_provider_url>`: User's Ethereum RPC provider connection address. 
+  - Default: `http://localhost:8545`
+  - Mainnet: `https://ethereum-rpc.publicnode.com`
+  - Holesky: `https://ethereum-holesky-rpc.publicnode.com`
+  - Also, you can use your own Ethereum RPC providers.
+- `--beacon_client_url <BEACON_CLIENT_URL>`: User's Ethereum Consensus provider connection address. Public nodes don't support this method.
+
+
+
+#### Example:
+
+```bash
+aligned verify-agg-proof \
+  --network holesky \
+  --from-block 3638552 \
+  --proving_system SP1 \
+  --public_input ../../scripts/test_files/sp1/sp1_fibonacci_4_1_3.pub \
+  --vk ./scripts/test_files/sp1/sp1_fibonacci_4_1_3.vk \
+  --beacon_url <YOUR_BEACON_CLIENT> \
+  --rpc_url https://ethereum-holesky-rpc.publicnode.com
+```