graphsense-python 2.13.2__py3-none-any.whl → 2.13.5__py3-none-any.whl
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- graphsense/__init__.py +2 -2
- graphsense/api/addresses_api.py +1 -1
- graphsense/api/blocks_api.py +1 -1
- graphsense/api/bulk_api.py +1 -1
- graphsense/api/clusters_api.py +1 -1
- graphsense/api/entities_api.py +1 -1
- graphsense/api/general_api.py +1 -1
- graphsense/api/rates_api.py +1 -1
- graphsense/api/tags_api.py +1 -1
- graphsense/api/tokens_api.py +1 -1
- graphsense/api/txs_api.py +1 -1
- graphsense/api_client.py +2 -2
- graphsense/configuration.py +3 -3
- graphsense/exceptions.py +1 -1
- graphsense/gs_files/__init__.py +2 -0
- graphsense/gs_files/encoder.py +369 -43
- graphsense/models/__init__.py +1 -1
- graphsense/models/actor.py +1 -1
- graphsense/models/actor_context.py +1 -1
- graphsense/models/address.py +1 -1
- graphsense/models/address_output.py +1 -1
- graphsense/models/address_tag.py +1 -1
- graphsense/models/address_tags.py +1 -1
- graphsense/models/address_tx.py +1 -1
- graphsense/models/address_tx_utxo.py +1 -1
- graphsense/models/address_txs.py +1 -1
- graphsense/models/block.py +1 -1
- graphsense/models/block_at_date.py +1 -1
- graphsense/models/change_heuristics.py +1 -1
- graphsense/models/cluster.py +1 -1
- graphsense/models/cluster_addresses.py +1 -1
- graphsense/models/coin_join_consensus.py +1 -1
- graphsense/models/coin_join_heuristics.py +1 -1
- graphsense/models/concept.py +1 -1
- graphsense/models/consensus_entry.py +1 -1
- graphsense/models/currency_stats.py +1 -1
- graphsense/models/direct_change_heuristic.py +1 -1
- graphsense/models/entity.py +1 -1
- graphsense/models/entity_addresses.py +1 -1
- graphsense/models/external_conversion.py +1 -1
- graphsense/models/http_validation_error.py +1 -1
- graphsense/models/join_market_heuristic.py +1 -1
- graphsense/models/label_summary.py +1 -1
- graphsense/models/labeled_item_ref.py +1 -1
- graphsense/models/link.py +1 -1
- graphsense/models/link_utxo.py +1 -1
- graphsense/models/links.py +1 -1
- graphsense/models/links_inner.py +1 -1
- graphsense/models/location_inner.py +1 -1
- graphsense/models/multi_input_change_heuristic.py +1 -1
- graphsense/models/neighbor_address.py +1 -1
- graphsense/models/neighbor_addresses.py +1 -1
- graphsense/models/neighbor_cluster.py +1 -1
- graphsense/models/neighbor_clusters.py +1 -1
- graphsense/models/neighbor_entities.py +1 -1
- graphsense/models/neighbor_entity.py +1 -1
- graphsense/models/one_time_change_heuristic.py +1 -1
- graphsense/models/rate.py +1 -1
- graphsense/models/rates.py +1 -1
- graphsense/models/related_address.py +1 -1
- graphsense/models/related_addresses.py +1 -1
- graphsense/models/search_result.py +1 -1
- graphsense/models/search_result_by_currency.py +1 -1
- graphsense/models/search_result_level1.py +1 -1
- graphsense/models/search_result_level2.py +1 -1
- graphsense/models/search_result_level3.py +1 -1
- graphsense/models/search_result_level4.py +1 -1
- graphsense/models/search_result_level5.py +1 -1
- graphsense/models/search_result_level6.py +1 -1
- graphsense/models/stats.py +1 -1
- graphsense/models/tag.py +1 -1
- graphsense/models/tag_cloud_entry.py +1 -1
- graphsense/models/tag_summary.py +1 -1
- graphsense/models/taxonomy.py +1 -1
- graphsense/models/token_config.py +1 -1
- graphsense/models/token_configs.py +1 -1
- graphsense/models/tx.py +1 -1
- graphsense/models/tx_account.py +1 -1
- graphsense/models/tx_ref.py +1 -1
- graphsense/models/tx_summary.py +1 -1
- graphsense/models/tx_utxo.py +1 -1
- graphsense/models/tx_value.py +1 -1
- graphsense/models/user_reported_tag.py +1 -1
- graphsense/models/user_tag_report_response.py +1 -1
- graphsense/models/utxo_heuristics.py +1 -1
- graphsense/models/validation_error.py +1 -1
- graphsense/models/values.py +1 -1
- graphsense/models/wasabi_heuristic.py +1 -1
- graphsense/models/whirlpool_coin_join_heuristic.py +1 -1
- graphsense/models/whirlpool_tx0_heuristic.py +1 -1
- graphsense/rest.py +1 -1
- {graphsense_python-2.13.2.dist-info → graphsense_python-2.13.5.dist-info}/METADATA +20 -4
- graphsense_python-2.13.5.dist-info/RECORD +176 -0
- graphsense_python-2.13.2.dist-info/RECORD +0 -176
- {graphsense_python-2.13.2.dist-info → graphsense_python-2.13.5.dist-info}/WHEEL +0 -0
- {graphsense_python-2.13.2.dist-info → graphsense_python-2.13.5.dist-info}/entry_points.txt +0 -0
- {graphsense_python-2.13.2.dist-info → graphsense_python-2.13.5.dist-info}/top_level.txt +0 -0
graphsense/__init__.py
CHANGED
|
@@ -5,14 +5,14 @@
|
|
|
5
5
|
"""
|
|
6
6
|
GraphSense API
|
|
7
7
|
|
|
8
|
-
GraphSense API provides programmatic access to blockchain analytics data across multiple ledgers. Use it to explore addresses, clusters, blocks, transactions, tags, token activity, and exchange-rate context, and to integrate investigation workflows into your own applications and automation. ## Versioning
|
|
8
|
+
GraphSense API provides programmatic access to blockchain analytics data across multiple ledgers. Use it to explore addresses, clusters, blocks, transactions, tags, token activity, and exchange-rate context, and to integrate investigation workflows into your own applications and automation. ## Versioning & deprecation The API follows semantic versioning. Minor releases are additive and backwards-compatible; breaking changes only happen in major releases, which are rare and announced in advance. Deprecated endpoints and fields remain fully functional for at least six months after they are marked deprecated. During that window they are highlighted with a strikethrough in the docs and in generated clients, and responses from deprecated endpoints carry a `Deprecation` HTTP header that client tooling can detect. Replacement endpoints and fields are always introduced before the deprecated surface is removed. See the [full versioning and deprecation policy](https://github.com/graphsense/graphsense-lib/blob/master/README.md#rest-api-evolution-and-deprecation-policy) for details. ## AI assistant access (MCP) In addition to this REST API, this deployment exposes a **Model Context Protocol (MCP)** interface that lets AI assistants query GraphSense directly in natural language, without writing code against the endpoints below. The MCP interface is available at the `/mcp` path of this server, relative to the address this documentation is served from. It offers a curated selection of the most useful operations, so an assistant can answer questions about addresses, transactions, clusters, and tags on your behalf. To use it, add that `/mcp` URL to an MCP-capable assistant as a new connector or tool source; the assistant then handles the rest. # noqa: E501
|
|
9
9
|
|
|
10
10
|
Contact: contact@iknaio.com
|
|
11
11
|
Generated by: https://openapi-generator.tech
|
|
12
12
|
"""
|
|
13
13
|
|
|
14
14
|
|
|
15
|
-
__version__ = "2.13.
|
|
15
|
+
__version__ = "2.13.5"
|
|
16
16
|
|
|
17
17
|
# Define package exports
|
|
18
18
|
__all__ = [
|
graphsense/api/addresses_api.py
CHANGED
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
"""
|
|
4
4
|
GraphSense API
|
|
5
5
|
|
|
6
|
-
GraphSense API provides programmatic access to blockchain analytics data across multiple ledgers. Use it to explore addresses, clusters, blocks, transactions, tags, token activity, and exchange-rate context, and to integrate investigation workflows into your own applications and automation. ## Versioning
|
|
6
|
+
GraphSense API provides programmatic access to blockchain analytics data across multiple ledgers. Use it to explore addresses, clusters, blocks, transactions, tags, token activity, and exchange-rate context, and to integrate investigation workflows into your own applications and automation. ## Versioning & deprecation The API follows semantic versioning. Minor releases are additive and backwards-compatible; breaking changes only happen in major releases, which are rare and announced in advance. Deprecated endpoints and fields remain fully functional for at least six months after they are marked deprecated. During that window they are highlighted with a strikethrough in the docs and in generated clients, and responses from deprecated endpoints carry a `Deprecation` HTTP header that client tooling can detect. Replacement endpoints and fields are always introduced before the deprecated surface is removed. See the [full versioning and deprecation policy](https://github.com/graphsense/graphsense-lib/blob/master/README.md#rest-api-evolution-and-deprecation-policy) for details. ## AI assistant access (MCP) In addition to this REST API, this deployment exposes a **Model Context Protocol (MCP)** interface that lets AI assistants query GraphSense directly in natural language, without writing code against the endpoints below. The MCP interface is available at the `/mcp` path of this server, relative to the address this documentation is served from. It offers a curated selection of the most useful operations, so an assistant can answer questions about addresses, transactions, clusters, and tags on your behalf. To use it, add that `/mcp` URL to an MCP-capable assistant as a new connector or tool source; the assistant then handles the rest. # noqa: E501
|
|
7
7
|
|
|
8
8
|
Contact: contact@iknaio.com
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
graphsense/api/blocks_api.py
CHANGED
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
"""
|
|
4
4
|
GraphSense API
|
|
5
5
|
|
|
6
|
-
GraphSense API provides programmatic access to blockchain analytics data across multiple ledgers. Use it to explore addresses, clusters, blocks, transactions, tags, token activity, and exchange-rate context, and to integrate investigation workflows into your own applications and automation. ## Versioning
|
|
6
|
+
GraphSense API provides programmatic access to blockchain analytics data across multiple ledgers. Use it to explore addresses, clusters, blocks, transactions, tags, token activity, and exchange-rate context, and to integrate investigation workflows into your own applications and automation. ## Versioning & deprecation The API follows semantic versioning. Minor releases are additive and backwards-compatible; breaking changes only happen in major releases, which are rare and announced in advance. Deprecated endpoints and fields remain fully functional for at least six months after they are marked deprecated. During that window they are highlighted with a strikethrough in the docs and in generated clients, and responses from deprecated endpoints carry a `Deprecation` HTTP header that client tooling can detect. Replacement endpoints and fields are always introduced before the deprecated surface is removed. See the [full versioning and deprecation policy](https://github.com/graphsense/graphsense-lib/blob/master/README.md#rest-api-evolution-and-deprecation-policy) for details. ## AI assistant access (MCP) In addition to this REST API, this deployment exposes a **Model Context Protocol (MCP)** interface that lets AI assistants query GraphSense directly in natural language, without writing code against the endpoints below. The MCP interface is available at the `/mcp` path of this server, relative to the address this documentation is served from. It offers a curated selection of the most useful operations, so an assistant can answer questions about addresses, transactions, clusters, and tags on your behalf. To use it, add that `/mcp` URL to an MCP-capable assistant as a new connector or tool source; the assistant then handles the rest. # noqa: E501
|
|
7
7
|
|
|
8
8
|
Contact: contact@iknaio.com
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
graphsense/api/bulk_api.py
CHANGED
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
"""
|
|
4
4
|
GraphSense API
|
|
5
5
|
|
|
6
|
-
GraphSense API provides programmatic access to blockchain analytics data across multiple ledgers. Use it to explore addresses, clusters, blocks, transactions, tags, token activity, and exchange-rate context, and to integrate investigation workflows into your own applications and automation. ## Versioning
|
|
6
|
+
GraphSense API provides programmatic access to blockchain analytics data across multiple ledgers. Use it to explore addresses, clusters, blocks, transactions, tags, token activity, and exchange-rate context, and to integrate investigation workflows into your own applications and automation. ## Versioning & deprecation The API follows semantic versioning. Minor releases are additive and backwards-compatible; breaking changes only happen in major releases, which are rare and announced in advance. Deprecated endpoints and fields remain fully functional for at least six months after they are marked deprecated. During that window they are highlighted with a strikethrough in the docs and in generated clients, and responses from deprecated endpoints carry a `Deprecation` HTTP header that client tooling can detect. Replacement endpoints and fields are always introduced before the deprecated surface is removed. See the [full versioning and deprecation policy](https://github.com/graphsense/graphsense-lib/blob/master/README.md#rest-api-evolution-and-deprecation-policy) for details. ## AI assistant access (MCP) In addition to this REST API, this deployment exposes a **Model Context Protocol (MCP)** interface that lets AI assistants query GraphSense directly in natural language, without writing code against the endpoints below. The MCP interface is available at the `/mcp` path of this server, relative to the address this documentation is served from. It offers a curated selection of the most useful operations, so an assistant can answer questions about addresses, transactions, clusters, and tags on your behalf. To use it, add that `/mcp` URL to an MCP-capable assistant as a new connector or tool source; the assistant then handles the rest. # noqa: E501
|
|
7
7
|
|
|
8
8
|
Contact: contact@iknaio.com
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
graphsense/api/clusters_api.py
CHANGED
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
"""
|
|
4
4
|
GraphSense API
|
|
5
5
|
|
|
6
|
-
GraphSense API provides programmatic access to blockchain analytics data across multiple ledgers. Use it to explore addresses, clusters, blocks, transactions, tags, token activity, and exchange-rate context, and to integrate investigation workflows into your own applications and automation. ## Versioning
|
|
6
|
+
GraphSense API provides programmatic access to blockchain analytics data across multiple ledgers. Use it to explore addresses, clusters, blocks, transactions, tags, token activity, and exchange-rate context, and to integrate investigation workflows into your own applications and automation. ## Versioning & deprecation The API follows semantic versioning. Minor releases are additive and backwards-compatible; breaking changes only happen in major releases, which are rare and announced in advance. Deprecated endpoints and fields remain fully functional for at least six months after they are marked deprecated. During that window they are highlighted with a strikethrough in the docs and in generated clients, and responses from deprecated endpoints carry a `Deprecation` HTTP header that client tooling can detect. Replacement endpoints and fields are always introduced before the deprecated surface is removed. See the [full versioning and deprecation policy](https://github.com/graphsense/graphsense-lib/blob/master/README.md#rest-api-evolution-and-deprecation-policy) for details. ## AI assistant access (MCP) In addition to this REST API, this deployment exposes a **Model Context Protocol (MCP)** interface that lets AI assistants query GraphSense directly in natural language, without writing code against the endpoints below. The MCP interface is available at the `/mcp` path of this server, relative to the address this documentation is served from. It offers a curated selection of the most useful operations, so an assistant can answer questions about addresses, transactions, clusters, and tags on your behalf. To use it, add that `/mcp` URL to an MCP-capable assistant as a new connector or tool source; the assistant then handles the rest. # noqa: E501
|
|
7
7
|
|
|
8
8
|
Contact: contact@iknaio.com
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
graphsense/api/entities_api.py
CHANGED
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
"""
|
|
4
4
|
GraphSense API
|
|
5
5
|
|
|
6
|
-
GraphSense API provides programmatic access to blockchain analytics data across multiple ledgers. Use it to explore addresses, clusters, blocks, transactions, tags, token activity, and exchange-rate context, and to integrate investigation workflows into your own applications and automation. ## Versioning
|
|
6
|
+
GraphSense API provides programmatic access to blockchain analytics data across multiple ledgers. Use it to explore addresses, clusters, blocks, transactions, tags, token activity, and exchange-rate context, and to integrate investigation workflows into your own applications and automation. ## Versioning & deprecation The API follows semantic versioning. Minor releases are additive and backwards-compatible; breaking changes only happen in major releases, which are rare and announced in advance. Deprecated endpoints and fields remain fully functional for at least six months after they are marked deprecated. During that window they are highlighted with a strikethrough in the docs and in generated clients, and responses from deprecated endpoints carry a `Deprecation` HTTP header that client tooling can detect. Replacement endpoints and fields are always introduced before the deprecated surface is removed. See the [full versioning and deprecation policy](https://github.com/graphsense/graphsense-lib/blob/master/README.md#rest-api-evolution-and-deprecation-policy) for details. ## AI assistant access (MCP) In addition to this REST API, this deployment exposes a **Model Context Protocol (MCP)** interface that lets AI assistants query GraphSense directly in natural language, without writing code against the endpoints below. The MCP interface is available at the `/mcp` path of this server, relative to the address this documentation is served from. It offers a curated selection of the most useful operations, so an assistant can answer questions about addresses, transactions, clusters, and tags on your behalf. To use it, add that `/mcp` URL to an MCP-capable assistant as a new connector or tool source; the assistant then handles the rest. # noqa: E501
|
|
7
7
|
|
|
8
8
|
Contact: contact@iknaio.com
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
graphsense/api/general_api.py
CHANGED
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
"""
|
|
4
4
|
GraphSense API
|
|
5
5
|
|
|
6
|
-
GraphSense API provides programmatic access to blockchain analytics data across multiple ledgers. Use it to explore addresses, clusters, blocks, transactions, tags, token activity, and exchange-rate context, and to integrate investigation workflows into your own applications and automation. ## Versioning
|
|
6
|
+
GraphSense API provides programmatic access to blockchain analytics data across multiple ledgers. Use it to explore addresses, clusters, blocks, transactions, tags, token activity, and exchange-rate context, and to integrate investigation workflows into your own applications and automation. ## Versioning & deprecation The API follows semantic versioning. Minor releases are additive and backwards-compatible; breaking changes only happen in major releases, which are rare and announced in advance. Deprecated endpoints and fields remain fully functional for at least six months after they are marked deprecated. During that window they are highlighted with a strikethrough in the docs and in generated clients, and responses from deprecated endpoints carry a `Deprecation` HTTP header that client tooling can detect. Replacement endpoints and fields are always introduced before the deprecated surface is removed. See the [full versioning and deprecation policy](https://github.com/graphsense/graphsense-lib/blob/master/README.md#rest-api-evolution-and-deprecation-policy) for details. ## AI assistant access (MCP) In addition to this REST API, this deployment exposes a **Model Context Protocol (MCP)** interface that lets AI assistants query GraphSense directly in natural language, without writing code against the endpoints below. The MCP interface is available at the `/mcp` path of this server, relative to the address this documentation is served from. It offers a curated selection of the most useful operations, so an assistant can answer questions about addresses, transactions, clusters, and tags on your behalf. To use it, add that `/mcp` URL to an MCP-capable assistant as a new connector or tool source; the assistant then handles the rest. # noqa: E501
|
|
7
7
|
|
|
8
8
|
Contact: contact@iknaio.com
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
graphsense/api/rates_api.py
CHANGED
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
"""
|
|
4
4
|
GraphSense API
|
|
5
5
|
|
|
6
|
-
GraphSense API provides programmatic access to blockchain analytics data across multiple ledgers. Use it to explore addresses, clusters, blocks, transactions, tags, token activity, and exchange-rate context, and to integrate investigation workflows into your own applications and automation. ## Versioning
|
|
6
|
+
GraphSense API provides programmatic access to blockchain analytics data across multiple ledgers. Use it to explore addresses, clusters, blocks, transactions, tags, token activity, and exchange-rate context, and to integrate investigation workflows into your own applications and automation. ## Versioning & deprecation The API follows semantic versioning. Minor releases are additive and backwards-compatible; breaking changes only happen in major releases, which are rare and announced in advance. Deprecated endpoints and fields remain fully functional for at least six months after they are marked deprecated. During that window they are highlighted with a strikethrough in the docs and in generated clients, and responses from deprecated endpoints carry a `Deprecation` HTTP header that client tooling can detect. Replacement endpoints and fields are always introduced before the deprecated surface is removed. See the [full versioning and deprecation policy](https://github.com/graphsense/graphsense-lib/blob/master/README.md#rest-api-evolution-and-deprecation-policy) for details. ## AI assistant access (MCP) In addition to this REST API, this deployment exposes a **Model Context Protocol (MCP)** interface that lets AI assistants query GraphSense directly in natural language, without writing code against the endpoints below. The MCP interface is available at the `/mcp` path of this server, relative to the address this documentation is served from. It offers a curated selection of the most useful operations, so an assistant can answer questions about addresses, transactions, clusters, and tags on your behalf. To use it, add that `/mcp` URL to an MCP-capable assistant as a new connector or tool source; the assistant then handles the rest. # noqa: E501
|
|
7
7
|
|
|
8
8
|
Contact: contact@iknaio.com
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
graphsense/api/tags_api.py
CHANGED
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
"""
|
|
4
4
|
GraphSense API
|
|
5
5
|
|
|
6
|
-
GraphSense API provides programmatic access to blockchain analytics data across multiple ledgers. Use it to explore addresses, clusters, blocks, transactions, tags, token activity, and exchange-rate context, and to integrate investigation workflows into your own applications and automation. ## Versioning
|
|
6
|
+
GraphSense API provides programmatic access to blockchain analytics data across multiple ledgers. Use it to explore addresses, clusters, blocks, transactions, tags, token activity, and exchange-rate context, and to integrate investigation workflows into your own applications and automation. ## Versioning & deprecation The API follows semantic versioning. Minor releases are additive and backwards-compatible; breaking changes only happen in major releases, which are rare and announced in advance. Deprecated endpoints and fields remain fully functional for at least six months after they are marked deprecated. During that window they are highlighted with a strikethrough in the docs and in generated clients, and responses from deprecated endpoints carry a `Deprecation` HTTP header that client tooling can detect. Replacement endpoints and fields are always introduced before the deprecated surface is removed. See the [full versioning and deprecation policy](https://github.com/graphsense/graphsense-lib/blob/master/README.md#rest-api-evolution-and-deprecation-policy) for details. ## AI assistant access (MCP) In addition to this REST API, this deployment exposes a **Model Context Protocol (MCP)** interface that lets AI assistants query GraphSense directly in natural language, without writing code against the endpoints below. The MCP interface is available at the `/mcp` path of this server, relative to the address this documentation is served from. It offers a curated selection of the most useful operations, so an assistant can answer questions about addresses, transactions, clusters, and tags on your behalf. To use it, add that `/mcp` URL to an MCP-capable assistant as a new connector or tool source; the assistant then handles the rest. # noqa: E501
|
|
7
7
|
|
|
8
8
|
Contact: contact@iknaio.com
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
graphsense/api/tokens_api.py
CHANGED
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
"""
|
|
4
4
|
GraphSense API
|
|
5
5
|
|
|
6
|
-
GraphSense API provides programmatic access to blockchain analytics data across multiple ledgers. Use it to explore addresses, clusters, blocks, transactions, tags, token activity, and exchange-rate context, and to integrate investigation workflows into your own applications and automation. ## Versioning
|
|
6
|
+
GraphSense API provides programmatic access to blockchain analytics data across multiple ledgers. Use it to explore addresses, clusters, blocks, transactions, tags, token activity, and exchange-rate context, and to integrate investigation workflows into your own applications and automation. ## Versioning & deprecation The API follows semantic versioning. Minor releases are additive and backwards-compatible; breaking changes only happen in major releases, which are rare and announced in advance. Deprecated endpoints and fields remain fully functional for at least six months after they are marked deprecated. During that window they are highlighted with a strikethrough in the docs and in generated clients, and responses from deprecated endpoints carry a `Deprecation` HTTP header that client tooling can detect. Replacement endpoints and fields are always introduced before the deprecated surface is removed. See the [full versioning and deprecation policy](https://github.com/graphsense/graphsense-lib/blob/master/README.md#rest-api-evolution-and-deprecation-policy) for details. ## AI assistant access (MCP) In addition to this REST API, this deployment exposes a **Model Context Protocol (MCP)** interface that lets AI assistants query GraphSense directly in natural language, without writing code against the endpoints below. The MCP interface is available at the `/mcp` path of this server, relative to the address this documentation is served from. It offers a curated selection of the most useful operations, so an assistant can answer questions about addresses, transactions, clusters, and tags on your behalf. To use it, add that `/mcp` URL to an MCP-capable assistant as a new connector or tool source; the assistant then handles the rest. # noqa: E501
|
|
7
7
|
|
|
8
8
|
Contact: contact@iknaio.com
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
graphsense/api/txs_api.py
CHANGED
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
"""
|
|
4
4
|
GraphSense API
|
|
5
5
|
|
|
6
|
-
GraphSense API provides programmatic access to blockchain analytics data across multiple ledgers. Use it to explore addresses, clusters, blocks, transactions, tags, token activity, and exchange-rate context, and to integrate investigation workflows into your own applications and automation. ## Versioning
|
|
6
|
+
GraphSense API provides programmatic access to blockchain analytics data across multiple ledgers. Use it to explore addresses, clusters, blocks, transactions, tags, token activity, and exchange-rate context, and to integrate investigation workflows into your own applications and automation. ## Versioning & deprecation The API follows semantic versioning. Minor releases are additive and backwards-compatible; breaking changes only happen in major releases, which are rare and announced in advance. Deprecated endpoints and fields remain fully functional for at least six months after they are marked deprecated. During that window they are highlighted with a strikethrough in the docs and in generated clients, and responses from deprecated endpoints carry a `Deprecation` HTTP header that client tooling can detect. Replacement endpoints and fields are always introduced before the deprecated surface is removed. See the [full versioning and deprecation policy](https://github.com/graphsense/graphsense-lib/blob/master/README.md#rest-api-evolution-and-deprecation-policy) for details. ## AI assistant access (MCP) In addition to this REST API, this deployment exposes a **Model Context Protocol (MCP)** interface that lets AI assistants query GraphSense directly in natural language, without writing code against the endpoints below. The MCP interface is available at the `/mcp` path of this server, relative to the address this documentation is served from. It offers a curated selection of the most useful operations, so an assistant can answer questions about addresses, transactions, clusters, and tags on your behalf. To use it, add that `/mcp` URL to an MCP-capable assistant as a new connector or tool source; the assistant then handles the rest. # noqa: E501
|
|
7
7
|
|
|
8
8
|
Contact: contact@iknaio.com
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
graphsense/api_client.py
CHANGED
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
"""
|
|
4
4
|
GraphSense API
|
|
5
5
|
|
|
6
|
-
GraphSense API provides programmatic access to blockchain analytics data across multiple ledgers. Use it to explore addresses, clusters, blocks, transactions, tags, token activity, and exchange-rate context, and to integrate investigation workflows into your own applications and automation. ## Versioning
|
|
6
|
+
GraphSense API provides programmatic access to blockchain analytics data across multiple ledgers. Use it to explore addresses, clusters, blocks, transactions, tags, token activity, and exchange-rate context, and to integrate investigation workflows into your own applications and automation. ## Versioning & deprecation The API follows semantic versioning. Minor releases are additive and backwards-compatible; breaking changes only happen in major releases, which are rare and announced in advance. Deprecated endpoints and fields remain fully functional for at least six months after they are marked deprecated. During that window they are highlighted with a strikethrough in the docs and in generated clients, and responses from deprecated endpoints carry a `Deprecation` HTTP header that client tooling can detect. Replacement endpoints and fields are always introduced before the deprecated surface is removed. See the [full versioning and deprecation policy](https://github.com/graphsense/graphsense-lib/blob/master/README.md#rest-api-evolution-and-deprecation-policy) for details. ## AI assistant access (MCP) In addition to this REST API, this deployment exposes a **Model Context Protocol (MCP)** interface that lets AI assistants query GraphSense directly in natural language, without writing code against the endpoints below. The MCP interface is available at the `/mcp` path of this server, relative to the address this documentation is served from. It offers a curated selection of the most useful operations, so an assistant can answer questions about addresses, transactions, clusters, and tags on your behalf. To use it, add that `/mcp` URL to an MCP-capable assistant as a new connector or tool source; the assistant then handles the rest. # noqa: E501
|
|
7
7
|
|
|
8
8
|
Contact: contact@iknaio.com
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
|
@@ -95,7 +95,7 @@ class ApiClient:
|
|
|
95
95
|
self.default_headers[header_name] = header_value
|
|
96
96
|
self.cookie = cookie
|
|
97
97
|
# Set default User-Agent.
|
|
98
|
-
self.user_agent = 'OpenAPI-Generator/2.13.
|
|
98
|
+
self.user_agent = 'OpenAPI-Generator/2.13.5/python'
|
|
99
99
|
self.client_side_validation = configuration.client_side_validation
|
|
100
100
|
|
|
101
101
|
def __enter__(self):
|
graphsense/configuration.py
CHANGED
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
"""
|
|
4
4
|
GraphSense API
|
|
5
5
|
|
|
6
|
-
GraphSense API provides programmatic access to blockchain analytics data across multiple ledgers. Use it to explore addresses, clusters, blocks, transactions, tags, token activity, and exchange-rate context, and to integrate investigation workflows into your own applications and automation. ## Versioning
|
|
6
|
+
GraphSense API provides programmatic access to blockchain analytics data across multiple ledgers. Use it to explore addresses, clusters, blocks, transactions, tags, token activity, and exchange-rate context, and to integrate investigation workflows into your own applications and automation. ## Versioning & deprecation The API follows semantic versioning. Minor releases are additive and backwards-compatible; breaking changes only happen in major releases, which are rare and announced in advance. Deprecated endpoints and fields remain fully functional for at least six months after they are marked deprecated. During that window they are highlighted with a strikethrough in the docs and in generated clients, and responses from deprecated endpoints carry a `Deprecation` HTTP header that client tooling can detect. Replacement endpoints and fields are always introduced before the deprecated surface is removed. See the [full versioning and deprecation policy](https://github.com/graphsense/graphsense-lib/blob/master/README.md#rest-api-evolution-and-deprecation-policy) for details. ## AI assistant access (MCP) In addition to this REST API, this deployment exposes a **Model Context Protocol (MCP)** interface that lets AI assistants query GraphSense directly in natural language, without writing code against the endpoints below. The MCP interface is available at the `/mcp` path of this server, relative to the address this documentation is served from. It offers a curated selection of the most useful operations, so an assistant can answer questions about addresses, transactions, clusters, and tags on your behalf. To use it, add that `/mcp` URL to an MCP-capable assistant as a new connector or tool source; the assistant then handles the rest. # noqa: E501
|
|
7
7
|
|
|
8
8
|
Contact: contact@iknaio.com
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
|
@@ -533,8 +533,8 @@ conf = graphsense.Configuration(
|
|
|
533
533
|
return "Python SDK Debug Report:\n"\
|
|
534
534
|
"OS: {env}\n"\
|
|
535
535
|
"Python Version: {pyversion}\n"\
|
|
536
|
-
"Version of the API: 2.13.
|
|
537
|
-
"SDK Package Version: 2.13.
|
|
536
|
+
"Version of the API: 2.13.5\n"\
|
|
537
|
+
"SDK Package Version: 2.13.5".\
|
|
538
538
|
format(env=sys.platform, pyversion=sys.version)
|
|
539
539
|
|
|
540
540
|
def get_host_settings(self) -> List[HostSetting]:
|
graphsense/exceptions.py
CHANGED
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
"""
|
|
4
4
|
GraphSense API
|
|
5
5
|
|
|
6
|
-
GraphSense API provides programmatic access to blockchain analytics data across multiple ledgers. Use it to explore addresses, clusters, blocks, transactions, tags, token activity, and exchange-rate context, and to integrate investigation workflows into your own applications and automation. ## Versioning
|
|
6
|
+
GraphSense API provides programmatic access to blockchain analytics data across multiple ledgers. Use it to explore addresses, clusters, blocks, transactions, tags, token activity, and exchange-rate context, and to integrate investigation workflows into your own applications and automation. ## Versioning & deprecation The API follows semantic versioning. Minor releases are additive and backwards-compatible; breaking changes only happen in major releases, which are rare and announced in advance. Deprecated endpoints and fields remain fully functional for at least six months after they are marked deprecated. During that window they are highlighted with a strikethrough in the docs and in generated clients, and responses from deprecated endpoints carry a `Deprecation` HTTP header that client tooling can detect. Replacement endpoints and fields are always introduced before the deprecated surface is removed. See the [full versioning and deprecation policy](https://github.com/graphsense/graphsense-lib/blob/master/README.md#rest-api-evolution-and-deprecation-policy) for details. ## AI assistant access (MCP) In addition to this REST API, this deployment exposes a **Model Context Protocol (MCP)** interface that lets AI assistants query GraphSense directly in natural language, without writing code against the endpoints below. The MCP interface is available at the `/mcp` path of this server, relative to the address this documentation is served from. It offers a curated selection of the most useful operations, so an assistant can answer questions about addresses, transactions, clusters, and tags on your behalf. To use it, add that `/mcp` URL to an MCP-capable assistant as a new connector or tool source; the assistant then handles the rest. # noqa: E501
|
|
7
7
|
|
|
8
8
|
Contact: contact@iknaio.com
|
|
9
9
|
Generated by: https://openapi-generator.tech
|
graphsense/gs_files/__init__.py
CHANGED
|
@@ -18,6 +18,7 @@ Encode:
|
|
|
18
18
|
|
|
19
19
|
from .encoder import (
|
|
20
20
|
GsBuilder,
|
|
21
|
+
apply_hierarchical_layout,
|
|
21
22
|
builder_from_spec,
|
|
22
23
|
encode_gs_payload,
|
|
23
24
|
)
|
|
@@ -55,6 +56,7 @@ __all__ = [
|
|
|
55
56
|
"PathfinderId",
|
|
56
57
|
"PathfinderThing",
|
|
57
58
|
"UserTag",
|
|
59
|
+
"apply_hierarchical_layout",
|
|
58
60
|
"builder_from_spec",
|
|
59
61
|
"decode_gs",
|
|
60
62
|
"decode_gs_bytes",
|