WEBVTT

00:00:00.250 --> 00:00:05.881
Welcome to the AgenticEcom Schema Discovery guide. We'll use Magento Admin to review

00:00:05.939 --> 00:00:11.419
the setup and explain the handoff to your headless storefront. This walkthrough covers

00:00:11.465 --> 00:00:16.643
stable version 1 point 0 point 2 and assumes the extension is installed.

00:00:17.693 --> 00:00:23.208
Open AgenticEcom, Sync Data, Schema Explorer. The viewer lists the

00:00:23.254 --> 00:00:28.873
queries and mutations available in your Magento GraphQL schema. This is an integration

00:00:28.943 --> 00:00:34.005
reference for your frontend developer; it does not grant a caller permission to execute protected

00:00:34.063 --> 00:00:35.247
operations.

00:00:36.297 --> 00:00:41.916
Use Refresh Schema after installing extensions or making changes that add GraphQL

00:00:42.032 --> 00:00:47.582
fields. Review the query and mutation lists, and use Download JSON when your developer

00:00:47.640 --> 00:00:52.888
needs the discovered schema. The refresh button belongs to Magento; Astro

00:00:52.969 --> 00:00:55.616
Admin has its own schema refresh step.

00:00:56.666 --> 00:01:02.204
Open Stores, Configuration, Schema Explorer, General. Review

00:01:02.262 --> 00:01:07.754
Allow Anonymous Schema Discovery. Keep anonymous discovery disabled unless your integration

00:01:07.823 --> 00:01:13.408
explicitly requires it and you have reviewed the exposure. It controls discovery of

00:01:13.466 --> 00:01:17.610
the schema, rather than normal authorisation of Magento data.

00:01:18.660 --> 00:01:24.337
Schema Sync Token is for the integration that retrieves schema discovery data. Keep it private

00:01:24.453 --> 00:01:29.376
and configure the corresponding storefront connection through your deployment's secret handling.

00:01:29.829 --> 00:01:35.285
After saving, refresh Schema Discovery in Astro Admin and confirm the expected fields are

00:01:35.320 --> 00:01:36.725
available to the editor.

00:01:37.775 --> 00:01:42.849
Check that a permitted schema-sync request works and that an unauthorised request is

00:01:42.918 --> 00:01:48.270
denied according to your settings. Then test the actual data query with the correct

00:01:48.340 --> 00:01:53.948
store and customer context. Discovering a mutation is different from being authorised

00:01:53.982 --> 00:01:59.509
to run it. No secret or external request is executed in this demonstration.

00:02:00.559 --> 00:02:05.621
Your next steps are to refresh the magento schema view, review discovery permissions and

00:02:05.679 --> 00:02:11.078
token, refresh astro schema and test access. Use a staging store for the

00:02:11.159 --> 00:02:16.360
end-to-end check. The complete installation and integration reference is at user guides dot

00:02:16.430 --> 00:02:18.485
AgenticEcom dot net.